Intermittent Problem with a Table on a Form

creative-petel

New member
Local time
Today, 23:17
Joined
Jan 22, 2008
Messages
2
I've just taken over looking after an Access 2003 database for a small business. In simple terms it is a bespoke booking system (dates, times, staff utilisation etc) for the services offered by the business.

The database is stored on a shared internal server and 2-3 client machines access the database during the day to add, edit and delete bookings and run reports. The current size of the database is >125Mb.

One of the forms used by the end-users contains a results table which queries the current bookings. The query is well formed in SQL and runs as expected on one machine. However, on the other two machines the table boundary shows but no data rows are displayed in the table. All other functions of the database are as expected and no other errors are displayed.

Is this a database problem or could this be a hardware issue? I'm confused as to how the table (and the underlying queries) run well on one machine but fail on two other machines, especially as the other functionality works fine on the two machines where I'm finding this fault. I'm told that the hard drive of one of the machines with the fault has recently been replaced.

Any help or advice on where to look would be appreciated.

I look forward to any replies....
 
RuralGuy - thanks for the tip about SP3. I've since found that the machine did have SP3 installed and have now installed the hotfix package.

However, I'm still getting the same problem where the results set isn't displaying in the table. Does anyone have any further ideas as to where I can look?
 
I'm afraid there are simply too many variables for me to pin down what is causing your issue. I also do not know if the HotFix resolved all of the issues of the SP3 update. If it is Access causing the problem, the only other solution I know is to reinstall Access and upgrade it stopping short of SP3. Sorry.
 
One basic problem to look for when things work on one machine but not the other is that there are things stored locally on the C: drive of the machine that functions properly. I've run into this when I forget to move a linked table to a shared area, and that linked table is buried in a query somewhere.
 

Users who are viewing this thread

Back
Top Bottom