I
Ian Millward
crosposted to microsoft.public.access.multiuser
I am developing a small Access DB on the hoof for about 3 or 4 users over a
small internal network but my network skills are minimal and there could lay
the problem.
In the version I gave them a couple of weeks ago, I forgot to put in
password protection and it worked fine. I sent out a later version this
week, with a simple DB level password protection, and it has crashed twice.
There are usually only two users connected at the same time. When one of
them closes Access it crashes on the other machine. It is a single DB on a
server, which they all have access to. I will split it out to a front and
back end later, together with User-Level Security but not yet for
conveniences sake. It is Access 2k/Win 2k on all machines. The last words
and testament are:
<<The Database "C:/MyDir" needs to be repaired or is not a database file.
You or anyone using it must have un-expectantly quit MS Access whilst a MS
Access Database was open. Do you want MS to try to repair the Database -
Yes/No>>
If "Yes" is clicked, a further message shows <<Not a valid password>> and
the Database cannot be accessed
Can anyone point me in the right direction?
Ian Millward
Edinburgh
I am developing a small Access DB on the hoof for about 3 or 4 users over a
small internal network but my network skills are minimal and there could lay
the problem.
In the version I gave them a couple of weeks ago, I forgot to put in
password protection and it worked fine. I sent out a later version this
week, with a simple DB level password protection, and it has crashed twice.
There are usually only two users connected at the same time. When one of
them closes Access it crashes on the other machine. It is a single DB on a
server, which they all have access to. I will split it out to a front and
back end later, together with User-Level Security but not yet for
conveniences sake. It is Access 2k/Win 2k on all machines. The last words
and testament are:
<<The Database "C:/MyDir" needs to be repaired or is not a database file.
You or anyone using it must have un-expectantly quit MS Access whilst a MS
Access Database was open. Do you want MS to try to repair the Database -
Yes/No>>
If "Yes" is clicked, a further message shows <<Not a valid password>> and
the Database cannot be accessed
Can anyone point me in the right direction?
Ian Millward
Edinburgh