Please help , frustrating problem .

[bahmadi]

Well , I have a really frustrating issue with this database .



I have a customer that are using an access 2003 database . I don't have any information or design layout of it . I could manage to get some information of it by spending lots of time . Here is all things that i know .

1- Access 2003 with the latest SP
2- lots of forms and tables .
3- tables are linked to SQL 2000 Database .
4- Users are using the application via Terminal services on windows 2K.

Issue
When a user run the application and wants to search a record she receive an error that say : "Job is currently being used" . There is no one using this job and she is the only person that is responsible to work with it . I took the following actions to fix it but it didn't work .
1- Restart the SQL service .
2- Restart the server .
3- Ran compact and repair command .
4- Check to see if any LDB file is open when nobody is using the database .
5- tried microsoft jet apps to compact it .

I really don't know what to do and I don't have any inofrmation of the person who created this database . It's very important to fix it ASAP .
Your help is appreciated .

[ajetrumpet]

I don't know if this helps, but there was some serious issues with Access that came as part of Office SP3. I remember seeing a page that Bob Larson put up years ago about that, but I don't have it anymore. The SP3 brought random issues to Access that didn't seem to have any pattern to them. It seemed as though anything and/or everything could happen.

I don't believe that the issues ever got resolved, actually. It's worth mentioning to you. If you see that website again, I'll certainly post it here.

[bahmadi]

I don't know if this helps, but there was some serious issues with Access that came as part of Office SP3. I remember seeing a page that Bob Larson put up years ago about that, but I don't have it anymore. The SP3 brought random issues to Access that didn't seem to have any pattern to them. It seemed as though anything and/or everything could happen.

I don't believe that the issues ever got resolved, actually. It's worth mentioning to you. If you see that website again, I'll certainly post it here.

Thank you for reply . They had this issue with service pack 2 . I though it can be fixed with service pack 3 . So I've installed SP3 but didn't help at all . Any Idea?
Thx

[RuralGuy]

There was also a HotFix that I believe was never incorporated in the Services Packs. http://support.microsoft.com/?id=970623

[RuralGuy]

You should also make sure that *every* user is using their own copy of the FrontEnd. Many think that this is not necessary with TerminalServer and they are wrong. They should have their own directory with their FE in it.

[RuralGuy]

Here's a link that could be useful: http://allenbrowne.com/bug-Access2003SP3.html