Login not properly functioning

[sareed23]

I have recently taken over IT responsibilities for this company and I a
very inexperienced with MS Access. They use an Access file that wa
created around year 2000, and it uses a mdw security login file.

I am currently upgrading machines from old NT machines to XP machines
and the users on the new machines are not being able to edit th
database any longer.

Originally, they would not get the login prompt, but I changed th
WRKGADM.EXE file to join the MDW file on our network server for thi
database. They then are able to login properly (if wrong username o
password it won't let them log into the database).

However, they customized switchboard they normally receive the data an
time and a greeting (Good morning, FirstName) on never shows up an
longer nor are they able to actually edit the data in the database.

Both the NT users and XP use MS Access 2000, I checked the ODBC driver
and the XP computers have the same drivers (plus some) as the NT one
just more recent versions). The directories are set so users ca
read/write to the structure.

Any ideas/thoughts

 

[Joan Wild]

Originally, they would not get the login prompt, but I changed the
WRKGADM.EXE file to join the MDW file on our network server for this
database. They then are able to login properly (if wrong username or
password it won't let them log into the database).

That's not a good idea - You've set their default mdw to the secure one,
which means they'll have to login for all databases, not just the secure
one. Usually you'd leave them joined by default to the standard system.mdw
that ships with Access and give them a desktop shortcut that uses the
/wrkgrp switch to point to the secure mdw for that session. The target
would look like
"path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure mdw"

However, they customized switchboard they normally receive the data
and time and a greeting (Good morning, FirstName) on never shows up
any longer nor are they able to actually edit the data in the
database.

It sounds like they are maybe opening the backend database (which is on the
server). You want them to have a copy of the frontend on their local
workstation, and have them open that (it would contain linked tables -
linked to the backend on the server).

Both the NT users and XP use MS Access 2000, I checked the ODBC
drivers and the XP computers have the same drivers (plus some) as the
NT ones just more recent versions). The directories are set so users
can read/write to the structure.

They also need create/delete permission on the server folder where the
backend is located.