Access 2010 Runtime, AutoExec Macro/Function call problem

I just developed an app in Access 2010, first time in 2010 but I've used prior versions of Access and prior versions of Sagekey for many, many years.

I tested everything on the app and created an installer using Sagekey 2010.  I then used the created installer to install the app on my local machines.  No issues whatsoever.  As designed the app install Access runtime 2010 as part of the install.

Possibly worth noting that even though the runtime 2010 was installed, all of the machines in the office have full versions of Access 2010 on them also.

Moved the app to my client site.  The only version of Access on those machines is Access 2003.

The application installed just as expected but cancelled in the Autoexec macro with 'function name cannot be found'.  The very first command in the Autoexec runs a function 'fRefreshlinks' to refresh the linked tables in the application.  If the tables aren't where the current links are pointing to, it  reads the information on an .ini file that tells where the data files are on this installation.

Never even executes 'fRefreshlinks', it cancel on the call to the function.

Does the runtime version of Access 2010 have limitations related to an Autoexec or maybe running functions?

I have used this exact same startup method for many years in Access 2003 without issue.

Any ideas what the issue is?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rey Obrero (Capricorn1)Commented:
<The only version of Access on those machines is Access 2003.>

access db created in higher version does not run smoothly or does not run at all in lower versions. There is no backward compatibility.

you may need to uninstall the clients Access 2003 and install access 2010 or use the 2010 runtime version.
The usual problem when an app runs on one PC but not on another is a reference issue.  Since you have only A2003 as a full install, there is no easy way to identify the specific reference that is missing.

Open the app on your PC and look at the referenced libraries.  If any are not installed on the target machine, or if the versions are lower, you will either need to upgrade the client PC or modify your code.  In some cases you can convert from early binding to late binding.
Rey Obrero (Capricorn1)Commented:

if it is not possible to upgrade your client access version, you have to develop/create the application using Access 2003.
Get Blueprints for Increased Customer Retention

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

I have been developing in A2010 for three years and I still have clients that have mixed environments.  As long as I don't actually use any A2010 features, late binding solves the reference issue.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Did you setup a Trusted Location with Sagekey? If not you need to do this. Generally you only need to do this for the FE location.

Also be careful of where the package is installed, if your client is using full blown Windows UAC. You'll have to install to ProgramData, or a folder immediately off the root drive, instead of Program Files in that instance.
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
I think Scott has probably hit it, but the other thing worth mentioning is that A2010 is far picker about references to things within an app.

Make sure your syntax is spot on.

Boyd (HiTechCoach) Trimmell, Microsoft Access MVPDesigner and DeveloperCommented:
Before any VBA code can be executed, the database must be trusted.

I agree with  Scott McDaniel that this is probably a trust issue not getting set by your setup/installer routines.

Windows 7 and Later and Access 2007 and later make deployment of application more difficult. This is for security reason to prevent malicious code from running. That does mean it will require more testing of your deployment packages.

I tested everything on the app and created an installer using Sagekey 2010.  I then used the created installer to install the app on my local machines.  

mlcktmguy, when you installed it on your local machine did you install it into a Virtual Machine (VM) that did not have any version of Access/Office previously  installed?

I find it best when testing installer packages to install it on a "Clean"/"fresh" version of Windows. This allows you to properly test all the settings your installer needs to handle.   Most VM have a fesature that allows you to create a snapshot and then roll back. This is great for repeated tests. Between test runs  you can roll back the Windows instance to the state before you ever tried ti install anything.  This gives you a "Clean" version of Windows each time.

I have VMs for multiple versions of Windows just for testing.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mlcktmguyAuthor Commented:
Thank you all great and valuable suggestions and comments.  Since the live date of the project was approaching, there simply wasn't time to resolve this issue.  My bad for waiting so long in the project cycle to test the install.

The issue has not yet been resolve but I will refer back to this thread when I have time to do so.  I'm sure the answer lies in one or many of these responses.

I did end up saving the app as an Access 2003 app and installing that way.  That brought it's own set up problems and additional tasks sine the complete menu system set up for 2010 had to be redone as well as several other items that did not have support in 2003.

Severe time crunch forced that decision

Props to all EE responders for providing such valuable and timely response in a very crucial situation.  I wish I could award more points to you all but 500 is the max.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.