Permissions Keep Changing

  • Thread starter Thread starter Guest
  • Start date Start date
TC - I had already done that prior to your helping me, but forgot to mention
it. Sorry. I haven't made any changes at all since working with you.
 
debug.print dbengine.systemdb
F:\shared\Share.mdw
debug.print dbengine(0)(0).name
G:\CIS\CIS-BACK.mdb
debug.print currentuser()
superuser
debug.print dbengine(0)(0).Containers("tables").documents("client").owner
SuperUser
debug.print
hex$(dbengine(0)(0).containers("tables").documents("client").allpermissions)
FFEFF
 
TC said:
Janet, I have a way forward which will quickly tell us what is going
on.

That is in a seperate reply. This reply is some general information for
you to consider in due course. //Do not change anything, yet, in
response to these comments!//





See below.



at one time).

Having a single FE is generally thought to increase the chances of
database corruption. It is true that having an FE per user gives rise
to an administrative problem, but there are various ways of handling
that. For example, there are "auto updater" modules that cause the FE
to automatically update itself, from a new version on the server,
whenever required. I recommend that you address this issue in due
course - but //not yet//, since it is unlikely to be the cause of your
current problem. So, //do not// change this yet.

OK




Mmmm. If you double-click the FE - or a simple shortcut to the FE -
this will use whatever workgroup file was last joined-to, on that PC.
By default - when Access is first installed, that file will be, the
default workgroup file on that PC. So, if the database is actually
opening (as it clearly is), one of two things must be true:

(a) You have used the workgroup administrator, on each PC, to join each
PC to the correct workgroup file on the server; or,

(b) The database will open with the PC's normal (default) workgroup
file. (This is common, & means that the database has not been properly
secured.)

I assume it is (a) - correct? YES THIS IS CORRECT If so, that is not the normal way to do
it, because that will cause the server's workgroup file to be used for
/every/ database on the PC - even ones that aren't secured. Those
local, unsecured databases should normally use the PC's initial,
default workgroup file.

Usually, you would use the shortcut described in 5, to open a secured
database. The shortcut uses the /wrkgrp switch to select the server
workgroup file /for that run only/. Then, you can leave each PC joined
to its normal (default) workgroup file, for running other (unsecured)
databases.

//Do not change this yet.// Leave it as it is, until we work out what
is causing your problem.




See 5. //Do not change this yet.//




Mmmm. Do you mean that you used the workgroup administrator program
/once/, on each PC, to join that PC to the workgroup file on the
server? Or do you use it repeatedly? If so, why?
Click to expand...

I used the Workgroup Administrator once on each computer to join it to the
MDW file associated with this database. However -- there are times when I
have to "redo" this on a few computers because somehow it magically defaulted
back to the system.mdw file -- then I get a call from the user that the
database won't open. No one seems to know how the computer was taken back to
the system.mdw. It's only happened a few times, and not lately.
 
Ok, sorry, I completely misread what you said :-(

As soon as you see that some table permissions have unexpectedly
changed, please post the before & after results of the (corrected!)
code that I gave you before. Then we'll soon see what is going on. Be
sure to cut & paste the exact text of each command's output. Pick one
of your own tables for this - do not use a system table.

Cheers :-)
TC
 
Next time that happens, and you start the workgroup administrator
program to correct it, please record exactly what the workgroup
administrator is displaying as the "current" workgroup file - ie.
/before/ you rejoin the correct file - then post that info. here.

Cheers,
TC
 
OK I'll do that. I will say that each time this has happened, I did notice
that the workgroup admin was displaying the original, default system.mdw file
joined.
 
Back
Top