2 identical PC's - database not working on one

[StuPalm]

Hi,

I've got a strange thing happening.

I have 2 identical PC's running the same Access database as separate apps on each machine. A very simple database for writing and printing delivery notes. I've copied the database from one machine to another so they are identical right down to the last record saved. The odd thing is that a query that works on one PC doesn't work on the other and therefore won't build the form for printing the delivery note. Any ideas on things I should be looking for? The version of Access is 2016 O365.

The two PCs were on domain on a small server but came off - network is now currently a workgroup, but as the PCs don't need to network to each other Access is running independently on each. When they were on domain both PCs worked with Access and the 'bad' PC was printing the delivery note i.e. the query was working. The query is a simple date extraction looking at the current today date (Date() in the expression builder) as delivery notes are dated and printed the same day.

Any thoughts - all trusts enabled etc.

 

[Minty]

What error are you getting ?

 

[isladogs]

There have been a few posts recently about issues some people are having with the latest update of Access via O365.

Check the Access build number on both PCs.
If different, try and make the bad PC build the same as the good PC.

 

[Frothingslosh]

At the 6000 person company where I work, we just updated my division to O365. So far, out of about 150 users for my apps, I've had four different applications break for individual machines. It was always a different machine each time, and only for a single app each time. In every case, that machine could run all other apps and all other users could run the affected app just fine.

*SO* aggravating.

In one case, a SQL statement used as a record property was being truncated by Access, even when the SQL was moved into a saved query and the record source set to the query's name.. In another, the application appeared to be running the Current event before the Open event.

Literally the only common issue is that the apps were compiled in a Windows 7/Access 2007 environment, since I'm getting upgraded last due to the reference issue caused when A2007 tries to open a file that has been touched by A2013 or later.

All I can suggest is to step through your code on the machine where it doesn't work, find the exact point where it's failing, and then we can see what we can do as a work-around.

 

[isladogs]

At the 6000 person company where I work, we just updated my division to O365. So far, out of about 150 users for my apps, I've had four different applications break for individual machines. It was always a different machine each time, and only for a single app each time. In every case, that machine could run all other apps and all other users could run the affected app just fine.

*SO* aggravating.

Hi Frothy

Have you been able to identify the issue in each case yet?

 

[AccessBlaster]

Sometimes I wonder if it's the ODBC driver vs native client, 64 vs 32.

 

[StuPalm]

Hi All,

You'll have to bear with me on this as I'm not a database programmer nor am I on site at the moment. However I've had some feedback from my user who has found a workaround to the problem.

I'll check the version number although that worries me as it probably means that the 'bad' PC is running a later version than the good PC. If the good PC updates that may break as well!!!

Basically all that happens in this app is that there is a table of client names and addresses to add to the Delivery Note, a table to hold the order details and a table to fill in line items on the delivery note. There are 2 dates that are input - 'Order Date' and 'Shipping Date'. Normally these can be the same and the query pulls the record that matches today's date, so in other words they enter order details and use the query to populate a page to print. The workaround is that the dates have to be DIFFERENT for the query to work on the bad PC. But they can be the same on the good PC.

Anyway, I'll go check version numbers this evening. Thanks for suggestions so far.

Best - Stu

 

[Frothingslosh]

Hi Frothy

Have you been able to identify the issue in each case yet?

No, I have not, unfortunately.

I would think AccessBlaster is correct (compiling via O365 instead of A2007 resolves it each time, but also removes them from our auto-update process, and the people still on A2007 can't use those copies), save for the fact that the vast majority of the upgraded machines have no issue with the applications.

 

[The_Doc_Man]

StuPalm, don't forget that references are not only something in the application, they also affect the registry and that is specific to each machine. Check for the failing database to have some broken references.

Since you claim to not be a programmer, what you do is open the DB on the failing machine, break out to the navigation panel, and open any module. From the VBA code window, look for Tools >> References and scroll through the top of that list of library names to see if any have the word "Missing" included in the entry.

That might not be it, but it is a simple and non-destructive test so it should be easy to do and easy on the code (minimum aftermath.)