Executable vs. .mde on other versions

[WindSailor]

I am currently working on a project that I am considering releasing (first release). The person that I am developing for is running Access 2000, and I am developing this in Access 2002 with the Developers package. I have read some on security issues and protecting my code with an .mde file.

Can I finish this in Access 2002, create and .mde file (2002 format) and then make an executable that will run on his system?

Will this .exe run also on/or using other versions of installed Access (older - 2000/97) without any conflicts (my immediate hunch is that this will be a stand alone project and will not use the older versions of Access - True?)?

Conflicts with older Operating Systems?

How about conflicts with older jet setups and vb versions?

I have read where other people have Access 2 through Access 2002 installed on their systems to ensure entigrity... wow! I don't know if I really want to do that, if there is a way to make this work by staying with 2002 I will do it; but if I have to install older versions then I will.

Thanks!

 

[pbaldy]

First of all, though I'm not sure, my understanding is that you can not make a 2000 mde with 2002. You can make an 2000 mdb, but not an mde.

Second, you can not make an exe at all. With the developer's version, you can distribute a runtime version of Access, but you will still be running an mdb or mde. I think the rest of your questions are moot considering that you can't make an exe. Let me know if I missed anything.

 

[WindSailor]

To my knowledge this is true... you can only make a mde with your version of Access only.

I went back and looked up some info and your right I can't make an executable, my mistake; but I can package the Access runtime which users that do not have Access installed will be able to run the mde file or whatever on their machine. So...

Can people who do and do not have (any) older versions of Access be able to run my packaged application (mde 2002 format) on their machines wothout any complications or conflicts?

I have never done this before and I have read where other people basically had all of the versions of Access installed on their machines to avoid conflicts; but realistically I didn't know if they didn't have the Developer Edition and just made mde files from the appropriate version of Access or there where underlying reasons why they did it this way. Again no experience here, just trying to avoid mistakes and get a little insight.


Thanks,
Rick

 

[Mile-O]

I am currently working on a project that I am considering releasing (first release). The person that I am developing for is running Access 2000, and I am developing this in Access 2002 with the Developers package. I have read some on security issues and protecting my code with an .mde file.

Develop it in 2002 if you have to, save it as Access 2000, and then - since the users are on Access 2000 - make an .mde front end from their machine which you can then distribute.

 

[alanj]

Complicating further...

I am in a similar situation, developing in Access XP (2002) but distributing to users who have older versions of Access, which they use for other work. I created a run-time version which installs nicely. If the client has no version of Access, or Access 97 / earlier, then the application runs without problems. If they have Access 2000, then their 2000 version initiates, and reports an error message saying it doesn't recognize the format.

HOW CAN I TELL MY APPLICATION TO RUN ONLY IN THE RUNTIME VERSION OF ACCESS??

 

[ghudson]

alanj,

I already answered your question in your other post
http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=57503