Important: Access 2010 packager, Sagekey Alternatives
My firm is a long time user of Sagekey for Access 2003.
We are scheduled to roll out an Access 2010 project this week. I ordered Sagekey 2010 online last Thursday and still hadn't gotten a download link as of today.
Finally called Sagekey and found out they are closed for the holidays and will not re-open until Jan2. I know, bad planning on our part but we are we we are.
My project has to be installed Jan 2 so this is a serious issue.
I have never used the Access 2010package creator. I would appreciate any information on how best to use it and what it does and doesn't do.
The application we are developing is for a network. The user machines do not have Access installed on them so the run time version of Access 2010 will have to be part of the install.
When using Sagekey, we put the installer on the network and gave all users a link to the installer on their desktops. When the link was clicked Sagekey would install the application, compete with the run time of Access on the local machine.
The installer included an .ini fle that contained the location of the data on the server. When the app was open on the local machine for the first time, we had a routine that would automatically link the files to the network.
This is the kind of functionality we are looking for.
We are scheduled to roll out an Access 2010 project this week. I ordered Sagekey 2010 online last Thursday and still hadn't gotten a download link as of today.
Finally called Sagekey and found out they are closed for the holidays and will not re-open until Jan2. I know, bad planning on our part but we are we we are.
My project has to be installed Jan 2 so this is a serious issue.
I have never used the Access 2010package creator. I would appreciate any information on how best to use it and what it does and doesn't do.
The application we are developing is for a network. The user machines do not have Access installed on them so the run time version of Access 2010 will have to be part of the install.
When using Sagekey, we put the installer on the network and gave all users a link to the installer on their desktops. When the link was clicked Sagekey would install the application, compete with the run time of Access on the local machine.
The installer included an .ini fle that contained the location of the data on the server. When the app was open on the local machine for the first time, we had a routine that would automatically link the files to the network.
This is the kind of functionality we are looking for.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can try www.FMSINC.com. It does a lot of what SageKey does but not all.
@PatHartman, would you mind sharing which FMS product creates an installer package and installs the Access runtime if needed?
@mlcktmguy, that is great news. Glad to here SageKey can through for you.
Total Access Startup. I sent an inquiry to them this morning regarding A2013 and some features. This is their response.
Thank you for your interest in Total Access Startup. The latest version of the product is designed to support Access 7.0, 97, 2000, 2002, 2003, 2007, and 2010. A version designed to support Access 2013 is currently in development.
We are planning to offer upgrade pricing for those users that have purchased one or more previous versions of this product. While no prices (or upgrade prices) have been set for upcoming product versions at this time, this is also something we will include in our notification to you when these products become available.
We do not yet have a date of release. However, since you have made this request, we will be sure to notify you upon the point it becomes available.
Total Access Startup does not offer a feature designed to setup trusted locations in the Windows registry. This task must be accomplished outside of Total Access Startup. The product is designed to support systems that are running multiple versions of Microsoft Access, however, it does not have the ability to suppress or prevent the re-initialization screen that you see when changing versions of Microsoft Access.
TAS is a "launcher", for lack of a better term, and not an installer. It would not install anything on the client machine, although it can update existing FE clients. It's a really cool tool, but it's not an installer.
ASKER
Props to Sagekey for going above and beyond the call of duty. Their product has been great in deploying Access 2003 apps and I'm hoping it will work the same for 2010.
Props to EE responder also for trying to help me out of what looked to be a very dire situation.