Installed Visio 2010 with Access 2007 applications. **Crash**

Thanks for the input but this option will never work in the real world.  My application is deployed to users using Access Runtime running accde (accdr).  After finding I was going to be in trouble if I didn't find a solution I decided to upgrade Office to 2010 and then upgrade the the DB to run under Access 2010 runtime.  WELL WELCOME TO A NEW WORLD OF PROBLEMS!!!  I am now finding that all the calculated fields in my Queries no longer work in Access 2010 runtime.  They work fine in the full version but the new runtime is missing some very important reference libraries or something which cause internal function calls to fail.  I have spent the last week trying to find a solution with no avail.  I can't force all users to use full version.  There is also a problem with compiling the file to accde.  Some of the Calculated queries no longer work even in the full version even if run in full version.  THANKS FOR THE UPGRADE MICROSOFT!!!!

I completely understand that it may not be feasible to repair Access each time, but that was just a proposed workaround to the issue you are running into. As mentioned, running multiple versions of Office on the same machine is not recommended, due to these types of problems.

 

290576           How to run multiple versions of Office on one computer

http://support.microsoft.com/default.aspx?scid=kb;EN-US;290576

 

 

As far as your calculated fields not working, I would say that this is most likely related to your compiling problem. If you are unable to compile the database into an ACCDE on the machine, then I wouldn’t expect your old ACCDE to function properly. The first thing I would check is open your VBA and ensure you don’t have any missing references. If you do have a missing reference, then you will need to either put the referenced files onto your machine in the proper location or uncheck the reference if it isn’t needed. In addition to this, what type of errors are you receiving when you try and compile your application? It may be a good idea to start a thread specific to the errors you are receiving when you try and compile it and hopefully one of us can help you resolve those.

 

Best Regards,

Nathan Ost

Microsoft Online Community Support

 

---

Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Nathan,

I did start a new thread.  I am able to compile the application fine without any errors.  All my references are fine and I am able to decompile and recompile without any issues.  All works fine under the full version of Access and when running accdb.  After compiling (without errors) to accde things start to fail especially when i try to run the app in Access runtime 2010.  After troubleshooting I did find that any call to Date functions or string functions fail in "Access Runtime 2010" when called from a Query.  They work fine in the full version of Access and when the file is accdb.   Also one final note.  All was working fine in this application and the calls from Queries in Access Runtime 2007 with the exception of string function calls (like Replace()) where I had to make a public Function in VBA to handle these calls.

Thanks again.

Sorry Nathan but I totally agree with TAGold on this one!  I have Office Developer and Visio is NOT part of it.  It is a separately purchased product.  Microsoft needs to get AWAY from the attitude that everyone will upgrade all versions of all of its products asap!  Best practice is to upgrade or modify ONE thing at a time, then test for problems so that if you encounter new ones you can more easily determine the root cause.  AND it is totally unacceptable for a NEW version to break the most recent OLD version.  All versions should be forward compatible accept when a single product is phasing out a functionality!!!!!

I too ran into the above problem.  Incidentally upgrading my Office developer to 2010 DID fix the issue. I haven't had it in long enough yet to see if other problems have arisen but I definitely did not do it until I had another machine effectively running Office 2007 so I could go BACK to it if I had to :)