I've put together a FM9 DB for a client, but have encountered some problems now that it's been launched on the server at the client site.

A "Work in Progress" layout includes a portal which displays work-in-progress for the currently-logged-in customer service rep. The layout is based on a "Users" table, and the portal is filtered to show only those jobs which are not marked as "invoiced" but that do list the user as the CSR for the job.

This works perfectly on my development machines, on the client's desktop, and also when uploaded to a FM hosting service.

However, when the DB is launched on my client's FM server, nothing appears in the portal. The appropriate jobs are all there (ie., are viewable in other layouts), but they do not appear in the portal. Sometimes if I work in the DB for a few minutes and then return to the layout in question, the jobs will apear in the portal, but this doesn't seem to happen reliably.

As far as I can tell, the relationship is set up correctly; as I said, the jobs appear as expected in every situation *except* when the DB is opened on the client's server. Could some server configuration issue be contributing to this issue? I'm the first to admit that I'm a novice when it comes to FMS/FMSA configuration. What kinds of questions should I be asking? Any suggestions about troubleshooting this?

If this *isn't* a server configuration issue, what else should I be examining?

Thanks in advance for your feedback. I really appreciate it.

I'm guessing that your portal uses in its relationship a global field that holds the logged in User ID. Are you setting that User ID in a startup script? Remember, global fields revert to the value that they had when the file was last opened single user. That would account for the "sometimes it works" behavior.