Errors on SOME client desktops running same database file

I have an Access 2003 database consisting of a 'front end' residing on four different desktops which are linked to tables residing on a server.
All clients are running XP Professional SP3.

On the rare occasions I need to make changes I do so, and then copy the client.mdb file to the other three desktops.  Yesterday, I added some new functions (using a query to output data to a file) to a module and copied the file over to the other desktops. The compiler reported no problems with my additions.

This morning we have two machines that present no problems whatsoever; one of which is mine.
The other two have multiple problems.

The most obvious (and easily described) occurs on the form which auto opens when the database is opened. There is an unbound text box which displays the current date using the date() function as its default value.
On the machines with the problems, #Name? is displayed instead.

I have ensured we are all opening the same copy!
The problem also occurs if one of the problem clients opens another client's copy across the network which works fine on that machine.
And now I discover the problem also occurs on older copies of the client mdb going back (so far) to last November.
The problem machines are fully patched and I've run Malwarebytes software on both with no issues reported.
Since it would appear to be machine specific I am at a total loss as to what the problem is and why it has suddenly occured!
Any help would be greatly appreciated.
Who is Participating?
Jeffrey CoachmanMIS LiasonCommented:
All Service packs installed for Windows and Office?

< Yesterday, I added some new functions (using a query to output data to a file) to a module>
Can you post this code?

< and copied the file over to the other desktops.>
Do you mean the MDE file, or the MDB file?
End users should be getting an MDE file, not really a MDB file (that they can possibly make design view changes to)

<The compiler reported no problems with my additions.>
To be clear, do you mean Debug-->Compile in the VB editor?
To be sure you should also run the Compact/Repair utility before distributing

Finally, try creating a blank new db and importing all the objects

Dale FyeCommented:
A recent Office Update (dated 14 Aug) may be responsible.  Don't know how to determine whether those machines have the update or not, but here is some information relating to the update and the associated fix.  

Check the references on the affected machine, if you have a MISSING reference to the Microsoft Common Controls (MSCOMCTL.OCX) file then this update could be the cause of your problems.
chrismkAuthor Commented:
Sadly that didn't work - in fact I discovered this morning that neither machine had used Microsoft Update last month - I performed that this morning and need to discover why they didn't - but I did follow your link and can confirm the registry entry and version values mentioned are correct.
However, they aren't for my machine which doesn't suffer the problem!

Since the problem occurs on much older files I don't think the problem is my recently added code. I did mean Debug-->Compile in the VB Editor and I did Compact/Repair before distributing.
They are both mdb files but point taken!
I'll try your last suggestion. I did remove everything from one of the files except for the entry form but the problem persisted.

Thank you both for your responses.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Dale FyeCommented:
Did you read the whole article, not just the Microsoft KB articles?  

The description at the bottom indicates that the problem is caused by the failure of the update to properly remove a previous registry entry.  If the computers with the problem ""are correct", then my guess is that they actually have encountered this problem, and you need to go through the steps described by FMS, not the ones in the KB articles, to repair the problem.

chrismkAuthor Commented:
Yes I did thanks!
As I said neither machine had received the update until after the problem has appeared.

As suggested by Jeff I have just created a new database on one of the problem machines and imported the form which had the date field.  It displays correctly!
I'll see what happens when I carefully import the remaining objects before reporting back sometime tomorrow now.

chrismkAuthor Commented:
Creating a blank new database on a problem machine and then importing the objects produced all sorts of failed macro/function messages.
So I created a new database and the importing on my good machine and copied that over to both the problem machines.
All seems well if no wiser as to the original cause!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.