database front end no responding

[marianieves1]

my database was moved to another location in the company drive in my absent. now, no user has been able to logging into the database. the database is divided in two, front end and back end, this last one only the admin has access to it. when trying to logging into the database front end a message pops up saying this:
The expression after update you entered as the event property setting produced the following error: could not find file;
* The expression may not result in the name of a macro, the name of a user-defined function, or event procedure
* there may have been an error evaluating the function, event, or macro.

[jimatqsi]

marianieves1,
Welcome to Bytes. You'll find this is a great place to get help with Access.

There's no magic bullet here. You have no choice but to move the file back or relink the front-end to the back-end and distribute the new front-end to all the users.

Jim

[jimatqsi]

I should add that you can may be able to get into the front-end by holding the shift key down when you run the program. The shift key MAY prevent any start-up script or form from launching. That feature can be turned off, so there is some uncertainty about it. Also, certain other factors can change that. Give it a shot.

Jim

[zmbd]

1) What version of Access are you using?

2) If you are using Access 2003 or earlier (*.MDB files), are you using "User Level Security"

3) Please clarify:

this last one only the admin has access to it

3a) Do you mean that you are using User Level Security, and only a user designated as an administrator within the database is able to gain access to the information
3b) Do you mean that only a user at the OS level, with and OS-Adminstrative User Profile, has read/write access to the backend file.

4) the following tells me:

The expression after update you entered as the event property setting produced the following error: could not find file;

That your front-end cannot find the backend files.
This is most likely because there was no prevision made by the programmer to handle file relocations. SIGH
AND/OR
if situation in question 3B is true, then the database cannot lock/access the backend properly.

The solution to this can be as simple as running the relinker from the database tools menu or as messy as having to restore the entire database to the origninal location. However, until we have an answer to questions 1, 2 and 3 I'm not sure which way to send you.