Newbies njbncv Posted February 24, 2006 Newbies Posted February 24, 2006 I have a developed a simple filemaker solution with few fields, but with over 100,000 records (75 mb). I would like to sell this database to the public as read only, with the ability to create labels and simple reports. Can I create a runtime solution that can be read and searched from a cd without downloading such a large file.
Newbies njbncv Posted February 27, 2006 Author Newbies Posted February 27, 2006 Please help! As you may can tell I am not an expert in Filemaker. Before I go to the expense of purchasing new filemaker software I want to make sure it will do what I want. Can you run a runtime solution off of a CD?
SteveB Posted February 27, 2006 Posted February 27, 2006 I don't think you can, since the CD is read only. Filemaker needs to work with files that are R/W. You could copy your solution to a temp folder and run it from there. Steve
Vaughan Posted February 27, 2006 Posted February 27, 2006 Don't do it in FMP 6 and earlier. FMP 7 and later has much better password and file encryption. If you lock down the interface and menu commands with passwords to limit the user's access you need not worry whether the files is copied to the hard disk or not.
Newbies njbncv Posted February 28, 2006 Author Newbies Posted February 28, 2006 It would be all right if the user downloads the file to their computer if that is what they want to do. I do not need to protect the file with a password. I just want to make sure the user can read and search the file straight from the cd on any windows computer.
CoZiMan Posted March 18, 2006 Posted March 18, 2006 I assume you want to keep the raw data locked. This means it has to be IN the database. You then need a two file solution. One small one that can be copied to disk for operations, and one that runs from the cd with all the data. This works fine for me. I used a simple web-page/html index file on the cd to point to the several Win/Mac interface files with file references to copy them to the users disk. Then all the interface files refer to the data file on the cd with 'related' fields for the results. Works great. You can strip the data from the data file for the interface file, and use a simple question at program load to locate the cd. Seems complex compared to 'installer' routines but it works pretty well and the data files don't hog the user's drive.
Recommended Posts
This topic is 6843 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now