Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MS Access 2003 ADP form stoped working 1

Status
Not open for further replies.

dougw1993

IS-IT--Management
Apr 28, 2009
1
US
Any help would be great full I help out a local non profit organization mostly on the server and desktop side of things. They have a case management application that they have been using for several years it has a Access 2003 ADP frontend and SQL 2000 back end “windows 2003 small business addition”.
One of the main input forms stopped accepting input the first part of April. The form opens ok but will not accept any input you can use the tab key to move between fields you can see the courser but the form will not accept any keyboard entries you don’t get any error messages or beeps it just won’t record any key strokes. I have two systems that I use for test machines one with just office 2003 and no office service packs and the form works ok on that system I have another that has office 2003 and service pack 2 and all of the resent updates with the exception of office service pack 3 and it works.

If I uninstall office and reinstall it with out office service pack 3 it works on most of the PC’s in the office there is one or two that still won’t accept input.
 
I'm not sure what your expertise is and I have only made 1 ADP and not had this issue but I'll make some guesses...

Down at the bottom of the screen if record selectors are turned on, it will show you the number of records. Is this a multiple of 10 like 10,000 or more? I think the default number of records an ADP will query is like 100,000. I forget where the setting is buried, in tools Options I think. If this is at all related the issue would be that different users are using different criteria. It doesn't seem like a fit but though I'd mention it.

Check the permissions in SQL server... Did any users leave groups and became effected? A simpler test of this would have a user who can't work log onto a machine that does... If it doesn't work it is the user not the machine.

Next on my list would be is the SQL server version / patch level conistent with the client drivers. It has been so long time since I've seen a problem with this. A contractor was doing the updates and we had WSUS for the clients so I'm sure everything would have been kept in sync by him.

That's all I can readily guess to check.
 
Thanks for the star, but would you mind posting which idea worked for you to help others?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top