"Record is deleted" message

[ppataki]

Dear All,

I have a database that is used by 20 users at the same time
They access tables through queries that are customized to their needs (approx 40 queries)

It happens oftentimes that they open a query and they get a Record is deleted message, and when trying to open the underlying table the same error message appears

When I compact the database the error is gone but certain records are gone as well!

Could you please advise?

Thank you!

 

[RuralGuy]

Have you split the application into FrontEnd and BackEnd and given everyone their own copy of the FrontEnd? http://allenbrowne.com/ser-01.html

 

[ppataki]

That is a good idea, I will try it

Many thanks!

 

[RuralGuy]

For a multi-user system it is way more than a good idea; it is a must! Otherwise, major corruption can occur.

 

[ppataki]

If I understand it correctly there is a frontend part with the forms and linked tables, and there is a backend part with the tables containing the data

My question is, if a user in the frontend opens a query then it will make the backend ineditable as well because an .ldb file gets created for the backend as well, right?
And also if I need to modify some forms or queries in the frontend I need to tell the users to quit the database, right?
or maybe I see it wrong

Could you please advise?
Many thanks

 

[Rabbie]

If I understand it correctly there is a frontend part with the forms and linked tables, and there is a backend part with the tables containing the data

Yes

My question is, if a user in the frontend opens a query then it will make the backend ineditable as well because an .ldb file gets created for the backend as well, right?

Locking should only occur if two users are trying to update/add the same record at the same time. No more a problem than if you don't split the DB.

And also if I need to modify some forms or queries in the frontend I need to tell the users to quit the database, right?
or maybe I see it wrong
Could you please advise?
Many thanks

No you just update the master copy of the FE and distribute that to your users. here is a link to a useful utility to make sure that all users have the correct version of the FE.

 

[RuralGuy]

Splitting the db makes modifying the front end available without kicking everyone off of the db. When you are done then you simply give everyone a fresh copy of the FrontEnd. There are free tools that can automate the process if you like. Using a query to open a table in the BackEnd does *not* lock up the BackEnd. It is the way it should be done rather than opening the table directly.

 

[ppataki]

Then maybe I do something incorrectly, but if I open a query in the frontend it locks the backend file as well
Pls see screenshot attached

Could you please advise?

Many many thanks!!

 

[JANR]

The backend will create and ldb file when someone opens his/her frontend, BUT it looks like ALL your user use the SAME frontend and that's is not correct. You are basically back to your starting point.

Your users should have their own copy of the frontend installed localy on his PC and liked to the backend.

JR

 

[ppataki]

Yes I understand that, but on the screenshot it is only me opening the frontend (so not more people) and still it locked the backend

is there a way to solve this?
My point is that even if 1 person enters the frontend it makes the backend ineditable, so what is the point in splitting the database then?

Thank you!

 

[JANR]

Here is an article on ldb files: http://support.microsoft.com/kb/136128/en-us

JR

 

[Rabbie]

Yes I understand that, but on the screenshot it is only me opening the frontend (so not more people) and still it locked the backend

is there a way to solve this?
My point is that even if 1 person enters the frontend it makes the backend ineditable, so what is the point in splitting the database then?

Thank you!

Just because there is a .ldb file does not mean the whole database is locked. It depends on the level of locking you have selected. I usually find that record level locking is the best. This means you can't have 2 people updating the same record.