Error 3008 opening form

[Gasman]

Hi all,

Just had this error in work when users are opening a form based on a query.
Last week I added a subform that shows multiple records for same case ref. However this data is not structured correctly (nor will it ever be, due to contraints outside my area), so the subform is also based the same table but via another slightly amended query. The form was 'Edited record' for locks, but I have since changed that to No locks as it is read only.

Now the puzzling thing is that this was installed last week and it was working fine as it was. I tested the previous day before issuing and had no problems.

First it was one user who got the 3008 error, and then a few more.

I quickly viewed the form and changed the record lock option on the subform.
Tried it out, OK. gave it to one user who had the 3008 problem, works OK. Gave it to anotehr user, does not work, same error.

I *think* this might be due to some running their FE accde file that somehow is locking the table via their form, but extremely puzzled as to why only some are affected.

Needless to say, management are anxious to get it back as before, as am I.

I intend for everyone to install the latest version tomorrow morning before work, but am looking for clues as to how this is ocurring?

TIA

 

[MarkK]

What error is 3008? When I raise it here I get an err.description of . . .

Application-defined or object-defined error

Do you get a more meaningful message? The err.description is more useful for trouble-shooting than the number.

 

[Gasman]

Hi Mark,

Thanks for the reply.

I don't have the exact error message, but it is along the lines of 'Table is opened by another user and cannot be opened in user interface or programatically'.

I'll try and get a screen dump from one of the users and post it.

 

[Gasman]

I cannot believe this.

I went to one of the users who were having the problem and asked them to open the database again so as to get the exact error message, and it opened fine. Went to the second user, same thing, and then the third, still OK.???

So someone appears to have been locking the table, but at present have no idea as to who. I have my suspicions as one team leader came out and back in again, since the problem ocurred, but was using the same version of accde as everyone else.??

None the wiser.

 

[bob fitz]

Has the db been split, with one backend file in a shared folder and each user having a copy of the frontend on their own machine, linked to the single backend file.

 

[Gasman]

Yes, Bob, that is exactly how it has been split. This was recommended on one of my first questions here.

I will not get time now to monitor this, but will have to wait and see if it occurs again.