Can't access db on user's machine

[Guest]

I'm dba for a new db (beta version) with User Level Security. There is a
user who is working through this beta version who comes up with suggestions
for improvement, and/or logic errors. The data tables sit on an SQL Server
and the 'front end' links to them.

After a recent modification to the db, the user can not access the db (which
is copied to a CD and then installed to her machine). On her machine, I
can't open the db, but I can on mine (same file). I've tried a 'Compact and
Repair Database...' without any luck. When she (or I) click on her desktop
icon which is a shortcut with the .mdw file, it brings up nothing (Access
opens, but the custom switchboard doesn't) . When I try it again, it creates
an error log, which I assume is telling me that there is already a lock file
on her machine. Deleting both of these lock files does nothing to fix the
problem.

Somehow, the file became corrupt. What should I be looking for to fix this
problem? There is last week's backup copy to revert to, but I would prefer
to not go that route.

I did another Compact and Repair Database again. Now the beta tester can log
on, but the load procedure craps out at when loading a form. For some
reason, the VB form info dies when loading.

Incidentally, I loaded this onto yet another machine and everything works
fine. It loads, I can write to the db, it saves, all the bells and whistles
work; even with multiple log-ons.

Could it be the beta user's pc that's causing the problem? If so, what can
be done about it; reload the app?

 

[Dirk Goldgar]

I'm dba for a new db (beta version) with User Level Security. There
is a user who is working through this beta version who comes up with
suggestions for improvement, and/or logic errors. The data tables
sit on an SQL Server and the 'front end' links to them.

After a recent modification to the db, the user can not access the db
(which is copied to a CD and then installed to her machine). On her
machine, I can't open the db, but I can on mine (same file). I've
tried a 'Compact and Repair Database...' without any luck. When she
(or I) click on her desktop icon which is a shortcut with the .mdw
file, it brings up nothing (Access opens, but the custom switchboard
doesn't) . When I try it again, it creates an error log, which I
assume is telling me that there is already a lock file on her
machine. Deleting both of these lock files does nothing to fix the
problem.

Somehow, the file became corrupt. What should I be looking for to
fix this problem? There is last week's backup copy to revert to, but
I would prefer to not go that route.

I did another Compact and Repair Database again. Now the beta tester
can log on, but the load procedure craps out at when loading a form.
For some reason, the VB form info dies when loading.

Incidentally, I loaded this onto yet another machine and everything
works fine. It loads, I can write to the db, it saves, all the bells
and whistles work; even with multiple log-ons.

Could it be the beta user's pc that's causing the problem? If so,
what can be done about it; reload the app?

I'm not sure exactly what's wrong, but the first thing I'd check is for
broken references on that user's PC. Often when databases don't work on
one particular machine, it's because of a broken or missing reference.
See if the steps outlined here help:


http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Can you open the database if you hold down the Shift key when opening
it, so that the startup logic doesn't run?

 

[Norman Yuan]

Now that the data table in on SQL Server, the "new db" is just a front end
app, and there is no need for User Level Security as regular Access database
(Jet database), because the data is secrued by SQL Server (either Windows
Integrated or SQL Server login).

Whether the other user (she) can connect to the SQL Server is depended on
the SQL Server settings: when she uses the app, the app passes user identity
(Windows Integrated Security) or user name/password (Sql Server Login) to
Sql Server, SQL Server then decides if the access is allowed or not).

You may want to make you clear how the SQL Server's security is set, so
that then you can tell how the front app is connected to it.

 

[Guest]

I'm not sure exactly what's wrong, but the first thing I'd check is for
broken references on that user's PC. Often when databases don't work on
one particular machine, it's because of a broken or missing reference.
See if the steps outlined here help:


http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Can you open the database if you hold down the Shift key when opening
it, so that the startup logic doesn't run?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

Thanks for the advice. The users that are having problems are all on W2K
OS, Access 2000. The db app was saved in A2k file format.

When they launch the shortcut from the desktop, their log on popup prompts
them for user name and password. That's good. When they enter their name
and pw and click OK, Access opens, but to a seemingly blank db. When they
'x' out to close the app, there is the error that says that MSACCESS.exe has
generated errors and will be closed by Windows.

When I hold the Shift key down as I click the OK button at log on, I get my
db window, but the forms don't launch; the tables are still there, but no
forms can be opened. Reestablishing the ODBC connection doesn't do any good.
I went through the References process outlined in your link, but that did no
good either.

This isn't a very good way to roll out an Access application and doesn't
bode well for my reputation either. Any other suggestions from anyone?

tiaa,
JMorrell

 

[Guest]

Thanks for your thoughts on this troubling issue.

Now that the data table in on SQL Server, the "new db" is just a front end
app, and there is no need for User Level Security as regular Access database
(Jet database), because the data is secrued by SQL Server (either Windows
Integrated or SQL Server login).

I'm using the user logon for access to certain forms, reports, etc. Logon
information is needed.

Whether the other user (she) can connect to the SQL Server is depended on
the SQL Server settings: when she uses the app, the app passes user identity
(Windows Integrated Security) or user name/password (Sql Server Login) to
Sql Server, SQL Server then decides if the access is allowed or not).

Connection to the SQL Server is happening without any trouble.

 

[Guest]

Chapter 1….
I'm dba for a new db (beta version) with User Level Security. There is a
user who is working through this beta version who comes up with suggestions
for improvement, and/or logic errors. The data tables sit on an SQL Server
and the 'front end' links to them.

After a recent modification to the db, the user can not access the db (which
is copied to a CD and then installed to her machine). On her machine, I
can't open the db, but I can on mine (same file). I've tried a 'Compact and
Repair Database...' without any luck. When she (or I) click on her desktop
icon which is a shortcut with the .mdw file, it brings up nothing (Access
opens, but the custom switchboard doesn't). When I try it again, it creates
an error log, which I assume is telling me that there is already a lock file
on her machine. Deleting both of these lock files does nothing to fix the
problem.

Somehow, the file became corrupt. What should I be looking for to fix this
problem? There is last week's backup copy to revert to, but I would prefer
to not go that route.

Chapter 2…
I did another Compact and Repair Database again. Now the beta tester can
log on, but the load procedure craps out at when loading a form. For some
reason, the VB form info dies when loading.

Incidentally, I loaded this onto yet another machine and everything works
fine. It loads, I can write to the db, it saves, all the bells and whistles
work; even with multiple logons.

Could it be the beta user's pc that's causing the problem? If so, what can
be done about it; reload the app

Chapter 3.......

Ok, I logged on to the user's pc with my network logon ID; I tried to launch
the app and it worked first time. I then logged off and the user logged on
with her network ID. She was able to open the app with no problems.

References all seem to be working.

She worked with the app for about 5 days, making notes as to the changes she
needs/wants. After making these adjustments to the app I copied the changes
to her pc and guess what? When she tried to open the app with the new
changes, she got the message "MSACCESS.EXE had to be shut down..." etc.

Chapter 4...

I went through the problem of removing all user level security (keeping a db
password) and tested it on my known good other test pc. Works just fine no
matter who logs on to that pc. Copied it to my user's pc and she can't open
it, I can't open it, no one can open it. The error now is that the user
doesn't have permission to open the db, see the administrator... etc. Trying
to enter with a bad password gets the error that says that it's a bad
password (so I know that part works, at least).

Questions...

Is it my user's pc? (She is running W2K Pro, Office 2000, and Access 2000.
I'm running XP Pro, Office 2003, and Access 2003. The whole db is saved as
an Access 2000 file format.)

What other files or gremlins could be causing this problem? I really need
some advice on this.

Thanks in advance,
JMorrell