Admin user gets different results when running code than when I do it.

[stildawn]

Hi All

I have a very complicated database that uses local access tables and Azure SQL tables etc, we have an admin person that adds new records to the database via a complex set of VBA / SQL code.

After an extensive update to the database, the admin person has twice now told me that they ran a spreadsheet (where the new data originally comes from) that didn't work, or only did half of the rows etc. I then then try it again using the exact same spreadsheet (original data) and the exact same version of the access database and the code works for me fine every time, both when I step through it and check each step, and when I run it all at once and check the final result.

So my question is, why does the same code result in something different for them, but not for me? It's making it very hard to bug check as I can't replicate what is happening for them. Is there anything that I am missing? Maybe like a different Windows setting or Access setting or something that could be causing the difference?

The two examples I have at the moment are:

1. A spreadsheet that for them didn't upload at all, Access ran through the code reporting no errors, but the new data just wasn't in the database at the end of the upload process.

- They emailed me the exact same spreadsheet and I ran it step by step in the same version and it worked fine, I also ran it again all at once (not stepping through the code) and it also worked, the end result being the data successfully in the database.

2. A spreadsheet that for them uploaded the first 102 rows of data and ignored the last 30 rows, Access ran through the code without errors etc.

- I tried it again on my end, and both stepping through and running the code all at once all 132 rows were uploaded correctly.

Any ideas?

[Welshgasman]

Yes. Logon as them, then try your debugging?

[stildawn]

Unfortunately they are in a different country so its not as easy as going across to their desk and trying it on their machine.

Logging into the access database as them will make no difference, its the exact same code they are running.

[Welshgasman]

Unfortunately they are in a different country so its not as easy as going across to their desk and trying it on their machine.

Logging into the access database as them will make no difference, its the exact same code they are running.

Suit yourself.
I was not expecting you to go to their computer and log on to that, not until that was the last resort, especially if they are far away.
There is such a thing as a remote connection?, I use it to support my sister and friends all the time?

If they are using exact same code then it would still be worthwhile logging on as them on your computer and see if you can replicate the problem?

When issues like this happen, I look at what is different, and in the easiest order to test.

Even worth making sure they have a fresh copy of the FE as well?

[ssanfu]

I'm with Welshgasman on this.

<snip>There is such a thing as a remote connection?, I use it to support my sister and friends all the time? <snip>

I use TeamViewer to help my Bonus Mom with her computer and Excel spreadsheets. Works slick and is free...

[Micron]

issue #1 suggests user rights to me. Issue #2 suggests hardware issue (as if part of the code runs too fast for the connection).
Logging on as affected user with your own pc won't address a hardware issue I'd say, and it can't be both reasons IMO. Lack of user rights doesn't allow for partial running of action queries (as in issue 2), right?

[orange]

If you both have Skype, you could do some screen sharing within Skype. But as ssanfu suggested Teamviewer is likely a better approach.
If you have tried logging on with the Admin account, and don't get the issue, then that would seem to point to hardware/configuration on the Admin's machine as micron suggested.