Yes, all users have full read/write permissions to the folder. They have
been accessing the db in that folder for years with no problem (until
recently the FE was on the server in that folder along with the BE and
mdw file and everyone logged into it there), and in fact the Auto FE
Updater worked for the first few days with no problem. And they can
still run the app from their computers using that mdw file as long as it
isn't done thru the Updater!

Very Odd!

Judy Reese
judyreese@comcast.net

No it isn't making any sense! But I have also decided that it has
nothing to do with the updater (although I will post my ini file at the
end of this email.)

Since posting my previous messages I have done further work on this and
the two machines that are getting this error message now get it
regardless of how they try to connect. I set up 3 different shortcuts on
one of the computers: one that uses the ini file and goes thru the
updater, one that points explicitly to the location of Access, the
location of the local copy of the mde file and the location of the mdw
file on the server, and another that is the same except that it points
to the location of the master mdb file on the server (and this is the
way all the users have been accessing the database for the last 8 years,
and have never had this error message before!) When it isn't working, it
won't work with any of these shortcuts!

The only thing so far that as worked on those two machines is to place a
copy of the mdw file on their local computer, which is obviously NOT
what I desire to do.  I have one other computer now, the one I use for
development work, which is also occasionally popping up with this error,
but it seems to be intermittant. All three of these machines are running
XP Pro SR2. None of the Win98 machines have so far had this error, to my
knowledge. At least two other WinXP machines have NOT had the problem,
and I hope to test others today.

Bottom line is that the problem apparently has nothing whatsover to do
with your updater utility. This database has been in use for 8 years,
with the files in the same locations they are now (except for now having
an mde file on each workstation) and this problem only cropped up last
week, shortly after setting up the Updater, which is why I assumed that
was the cause.

I have checked permissions, and even though the users had implicit
permissions for the folder as part of a group, I went ahead and granted
them explicit permissions, but that made no difference. (And I know one
of the gals was able to go to a different computer--Win98--and log in
and had no problem there, so it is specific to the computers, not the
accounts.)

I have a whole list of things to look into as I have opportunity --
virus software, Microsoft updates, Windows firewall, other software that
may have been installed, etc. etc. No clue how/why any of these could be
the problem but it seems it must be something specific to these
computers which has changed to cause this.

Sorry for the length of this post! Any suggestions would be appreciated.

Thanks
Judy

Ini file:
[Settings]
MainApp="C:\Program Files\FBCMembership\FBCMDAPP.MDE"
Server="H:\Users\1bofe\MDE\"
Lockout=No
LockoutMsg=The database is currently locked for maintenance. Please try
again later!
SupportMsg=Please contact Judy Reese for support.
CommandLine=/wrkgrp "H:\Users\1bofe\1BofE\Fbcwkgrp.mdw"

ShortCutName=FBC Membership
CreateShortCutOnDesktop=Yes
CreateShortCutOnCommonDesktop=No
ShortCutIconFile=H:\Users\1bofe\FE\FBC2.ico
ServerShortCutName=Setup_FBC_Mmbrshp
QuickLaunchShortCutName=FBC Membership
ShortcutErrorMessageHandling=2

MDWFile=H:\Users\1bofe\1BofE\Fbcwkgrp.mdw
MDWUser=JudyR
MDWPassword=(Password is encrypted)

MDWPasswordEncrypted=C42ED4AB55