The startup script does a few things, but the error appears as soon as it tries to set some explicit text values to global fields right at the beginning of the script. There is nothing tricky happening. just setting globals.

It doesn't do different things based on account names.

It doesn't open or access data in any other files.

I just tested, and I am able to login to the database using his account credentials from my computer via the WAN, so it must be something on his computer.

My client reported something similar. In his case, it's not affecting only him. I logged into the file, and the table in question is missing every field, like they've been deleted. The table still exists, and the TOs on the graph are still there (with the relationships being invalid now, because there are no fields in the table).

I pushed a fresh copy of the file to the server after deleting it from the host. It just happened again today, with a different table.

I also had a freak occurrence of a table going missing just the other day. Table was there but it was not. I did many things to try to correct this but luckily it was a table of global fields and there were only 5 fields. I deleted the table, closed the file, reopened, created the table again and fixed the few script references to use the new table.

Already submitted and in communication with TSGal on the issue. I'll report back here with whatever I discover.

I also agree that this sounds suspiciously like that issue. However, in my case the solution is a single-file solution (no hidden windows). But still, it seems as if FM is deleting the field catalog out of those tables...

I am also having the same problem: "This action cannot be performed because the required table is missing". This only occurs on one Mac. If that user logs into the same account on another Mac or iOS, the problem is gone. FileMaker has been uninstalled and reinstalled on the machine with the same result. If another user logs in on the problem machine, they do not have the problem. So only one account has the problem and only when logged onto the one machine.

I'm seeing this problem on Windows 10. When I log in no problem. When one of my users logs in he gets the message. The script is running a custom dialog box to collect values used in a find to present the user the records then need to deal with. I'm going to upgrade them to 17 to see if that resolves the issue. Our server is 16, I'm running 17 the user is running 15