I need to find out if the runtime version of Filemaker relies on any registry entries to function properly.

I have a Runtime program that I need to import data into to then be redistributed throughout our county. I was planning on installing it on my machine, importing the data, ZIPping the folder that was created after the install, then using NSIS zip to exe utility to create an "installer" that would copy the files to the user's computer.

Is this possible? Would it work properly?

I believe that doing it this way would not copy any registry files that were created during the original install (if ther were any).

If anybody is familiar with them, the programs are CAMEO and Landview (both would be done separate.

Thank You

I don't think that a runtime relies on the registry. However, if you use any fonts that are not on a user's machine, you'll have problems. Your best bet would be to move a runtime onto a machine that has never seen Filemaker, and see if it runs. Also, you might want to consider using an installer, so that the app appears on the user's desktop and the Start Menu.

Steve

Thank's alot Steve. I will give that a try. I just didn't know if maybe part would work and part not. I will try that out though.

I am working on using the installer NSIS. It is an open source program. It contains a utility that will take a regular zip file and turn it into a regular installer with status bar and all. It's really a nice little program, and you can't beat the price.

Thanks again.

Kevin

Steve is right - the runtime files themselves don't write to or rely on the registry at all. That's one of the nice things about it. So, if one ever wanted to remove the program, all you have to do is delete the files, instead of going to the Add/Remove Programs path.

A runtime will create its own registry entries the first time it is run. Look inside HKCUSoftwareFileMaker and you will see a key there with the same name as your program. It does not need to be there prior to running the program.

AFAICT it doesn't harm anything to leave that behind when doing an uninstall, so Brent is right, you simply need to delete the files.

J