Need directions to deploy my app 1

[Tomadams]

Hi - I created a single user application. I use 1 .mdb and only need a common dialog control to run the app. My customer now wants to provide this app to seven of their customers. I don't want my cource code out with people that did not pay for it. What is my process to provide the app, ensuring that it will work in unknown environments? It is in 2003 but uses DAO structures.
Thanks - Tom

 

[alvechurchdata]

I don't want my cource code out with people that did not pay for it.

If you build an MDE (it's under Tool|Database Utilities) then they won't be able to see your source code.

What is my process to provide the app, ensuring that it will work in unknown environments?

The only safe route is to test it on a clean PC in these environments. Life is a lot easier if you can agree with the client that the database will only be running under Windows XP Pro with the latest Service Packs. Life is a misery if they want it to run on every combination of PC and Windows.
I'm just trying to make one of our apps run in 640x480 video mode because that's what the customer uses. You wouldn't believe just how small that screen is.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[evalesthy]

You may also want to look into one of the packaging products to make your app easy to deliver and install.

InstallShield, Wise, SageKey all offer alternatives.

Here is one link:

http://www.sagekey.com/products/acc2003/msi.asp

 

[psemianonymous]

If you can swap from the common dialog control to a common dialog API call, you'll probably save time in the long run. And yes, there are API calls.

http://www.mvps.org/access/api/api0001.htm

My personal rule is to never use any nonstandard VBA references in Access apps because of the deployment headaches. Good luck.

 

[Tomadams]

Thanks for the tips - the app is being delivered as we speak.

pseale - can you answer two questions for me -
1 - what do I gain by using the API calls - what is the advantage
2 - what do you mean by non-standard vb code

thanks all
tom

 

[psemianonymous]

1. Using API calls means that you don't have to use the Common Controls library. This means that you don't have to ensure they have the same library installed on their PC (hint: they won't).


That is the pro and the con right there. Pro: deployment ease. Con: you can't use that library.