Presence of guid in definition of a table

  • Thread starter Thread starter Pat Williams
  • Start date Start date
P

Pat Williams

Access XP on Win 2K and XP systems,
I have a split fe/be database on the network.
Recently I wanted to simplify the directory structure that
the database had been working in, so created a new folder
and moved all the components into it -- the fe, be, and
Masterfolder w/ copy of fe.
Now, suddenly, all the users w/ "read/execute" only
privs are unable to open one of the tables in the
database, unless I give them "write" privs. There is no
Access security, so that table hasn't been given special
security limitations.
I notice that there is a GUID # in the _definition_ of
the table, not a field, and, if I compact/repair, or drag
the table into a new database, that guid # disappears only
to re-appear after I have opened the table once or twice.
I have eyeballed all the data (700 records, wide, but not
impossible) and can't find any obvious corruption.
I was concerned about replication after seeing that
GUID #'s were associated with replication (?), but I unhid
my system tables, and there is no MSReplicationWhatever
(<g> forgot name) table there that would indicate that
that is my problem.
Can anyone help me figure out the source of the
problem? I am beside myself!
thx
Pat Williams
 
Hi, Doug,

How does a GUID become a property in an Access 2002 table,
and will it be the cause of locking that will
knock "readonly" users out, and if so, how do I get rid of
it?

Or, can the presence of a subdatasheet in a table knock
out those folks with readonly access?

These are the only two things that distinguish this one
table on the network that will not allow users w/ readonly
access to access.

I've been concentrating on the GUID up 'til now, totally
spacing over the subdatasheet, but now that I've looked, I
don't find any warnings about making the table
inaccessible to readonly users.

I am not the main person who creates/modifies this
database, but I am the troubleshooter, which is why I
didn't notice the subdata sheet right away

I have compacted & repaired, dragged tables into a new
database, made "make table" queries where the guid will be
gone for two iterations and then suddenly reappear, and re-
recompacted and repaired, and nothing works.

I've run it in runtime mode, but I can't limit my privs
enough to really troubleshoot. I'm going to have to do
that, I don't _think_ there's anything wrong with the
form, but I may be missing something.

Once again, the GUID may not be the issue at all -- but I
have no clue, and I am also curious, because I seem to
find no information on a table property called GUID! (a
field,yes).

thx
Pat
 
Er ... an update <g>.
The problem is in the form -- somewhere. I tested that by
creating an exceedingly simple quick & dirty form, having
someone revert to readonly, and -- you can probably guess
it. I don't know why I ddin't check that earlier -- I
went through the form and couldn't find anything wrong,
but -- there it is. This GUID thing just led me down the
strippedy-horse path (I had a zebra all along).
thx
Pat
 
Back
Top