Question Slight Access 2010 XP problem.....

[carl6885]

Hi All

I am hoping someone can help me with this one.

I am developing an Access database for a company in London in my spare time. I develop these at work also.

All the work machines are running XP with Access 2010 runtime installed, obviously my dev machine has full version of Access 2010.

I develop and all works great at work.... my problem is the client is saying it is erroring all the time but I couldn't understand why as I have tested on an XP machine at work.

So i have come home tonight and installed a virtual version of XP with SP3 and Access Runtime 2010 and low and behold I have all the errors coming up.

Does anyone know why? It is very confusing with it all working OK at work.

Thanks in advance.

Carl

 

[DJkarl]

Well what kind of errors, specifically, are you getting in the runtime version vs the full version?

 

[carl6885]

Sorry, I am getting:

Execution of this application has stopped due to a run-time error. The application can't continue......

These are only happening in the runtime version on my virtual machine and the clients machine.

It all works perfectly in the full version of Access.

I am wondering if it is to do with the .Net framework on the computers??? i just installed .Net 3.5 on my virtual machine and some of the errors are not happening now!!!!

 

[gemma-the-husky]

well, ANY error you get in an mdb will immediately stop a run-time.

There may be other issues that a mdb can resolve (including reference issues, perhaps), that are not possible to resolve in runtime.

becuase of all this, you have to be very careful about development for a run time environment

So are you always getting the same error? if so, what error do you get? or does it break at different points, depending on what you are doing?

 

[vbaInet]

Once you've located the root cause and fixed that (like gemma-the-husky has mentioned), you need to build-in proper Error Handling in your db. Have error handling routines in all your functions/subs. Runtime databases crash if an error occurs and it's not handled.

 

[carl6885]

Hi Both

Thanks for the responses.

vbaInet, I do have a thorough error handling function that alerts the user as well as logging to a data table with the option of emailing the error or dumping the error tables to an excel document for sending at a later time. this is what made it confusing as it wasn't coming up with any error messages.

I searched my code many times to look for code missing the error handling to no prevail.

However i did solve the issue and yet another example of me being a newbie!

I had reference to Outlook 2010 and the system running it didn't have it installed, Access warned them about it but after passing the error they were able to use the database. However it kept generating a runtime error even if the code was not using the reference.

I set up a virtual machine to replicate that of the user machines and found that removing the reference it worked perfectly. This has now been confirmed by the users!

Thanks again for your comments.

Carl

 

[vbaInet]

Good to hear that you found the culprit and thanks for getting back.