Unable to split A2K unsecured database

[YACHTIE]

I have searched for some time for a solution or reason why I am unable to split a (inherited) database we use here @ my company.
It haS multiple users and never been secured,runs wide open for all, you can imagine the problems we run into.

So I decided it was time to bite the "database split" bullet (don't want to go secured with groups and passwords etc.)
But no matter what, I keep getting the message that says:
"tbl Eng Release Record could not be locked by the database engine because it is in use by another process or person"

According the ldb file I am the only one in the database.

My question: anyone has any idea what is preventing me from splitting this database???

A bit of history this database I believe was started in Access97 and migrated into 2000, all things considered it is usable and doing the job most of the time but I know we are on borrowed time so I need to improve security.

 

[Ed2020]

YACHTI,

Have you tried opening the database exclusively before you split? If that still doesn't work perhaps worth moving it onto your local drive before attempting the split.

I am still confused though - what additional security do you believe splitting is going to give you, over what you already have, without applying user-level security?

Ed Metcalfe.

Please do not feed the trolls.....

 

[YACHTIE]

Well, as I understand it it will at least keep the tables safe from inadvertendly being damaged or modified, I know if there is any intention of doing damage well... as you say feed the trolls....

It would I believe be somewhat safer then what we have today, the main problem here is that we have people not trained in Access doing unintentional damage or bad server infastructure none of which user level security would solve for us.

Hope that makes sense.
Now as far as doing what you suggested, have already tried both several times in several different scenarios without success that's why this has me stumped..

 

[YACHTIE]

Ed,
The other thing I should mention and correct me if I am wrong, but can I not limit write access thru network security to the back end? Currently we need to provide everyone with Access to the database write access to the folder where the table resides, which is not the case for the backend of a split database right?

However, finally I did manage to split the database by removing (turning off) the startup form and then re-adding it after the split, never heard or seen anything written that that causes a split prevent but go figure....

Thanks for your help,

 

[Ed2020]

YACHTIE,

No, users will still require write access if they need to save data changes to the database. If they are only querying the existing data then they don't necessarily require write access. Having said that this is possible without splitting the database.

Having tables in a backend may decrease the likelihood of damage by mistake, but users can easily find where the backend is stored and go and do whatever they want.

User level security will prevent users doing unintentional damage. It will also prevent most people from doing intentional damage, although Access security is crackable.

If you are still unable to split the database then I would suggest creating a new, blank MDB, importing all objects, and then using this as your starting point for splitting into a FE/BE.

Ed Metcalfe.

Please do not feed the trolls.....

 

[YACHTIE]

Still have trouble understanding why the startup form would prohibit me from splitting the database??

Anyone have any ideas on that one??
Anything to do with naming?? the form in question has the same name as one of the tables??