Hello — I’ve searched Microsoft for the answer, but can’t seem to phrase the keywords exactly right.
I have a split database, both FE/BE at the same location on the network. Users are secured through network, not Access securities. Most have read-only access, a couple have write. The read-only group crashes each and every time when opening a form or report involving one table, but not any of the others. If I upgrade the user to “write” privs for testing, they are fine. This is the Parent table, and it will crash if it’s just being opened plain, as the single recordsource behind one form. I can’t see anything unusual or different about form properties or my code. I’ve checked whether myself or another user w/ full Access is opening the whole database in “shared” mode (tho, that would affect all tables…) I “documented” table properties to see if I could identify a difference, and the one thing that jumped out was that only the problem table had a GUID string. This is the table I had test accessed using various methods to link, import data by code or by pass-through query, various other things in a separate database, and two tables and a form in that database also show a Guid # — I don’t know if that is normal, or not. Does anyone have any clues?
This problem seemed to begin after I moved a FE/BE database on the network, but they may have happened prior, but no one noticed. Also, one of the network administrators, even, had trouble accessing the folder I initially moved the databases into, which was exceedingly wierd. We created yet another new folder, and that problem has disappeared. I don’t think this is related to the problem, but, who knows.
Thanks very much, anyone who made it through this long-winded explanation, and/or might have some suggestions.
thx
Pat
