Runtime Solution will open in FM5

[printit]

I've created a run time solution in File Maker 5

My problem is anyone with file maker can open the files if they have the password.

I've tried locking the .EXE file with InterLoc from PACE but that dose no good sense skip over the .EXE file, I also tired locking some of the .DLL files

But that didn't work either sense File Maker uses its owned .DLL

I'm using InterLoc because I want to be able to supply my customers with a timed DEMO.

Any help would be AWASOME

I've racked my head on this one!!

Thanks Ron Bascom

[Kurt Knippel]

quote:

---

Originally posted by printit:

I've created a run time solution in File Maker 5

My problem is anyone with file maker can open the files if they have the password.

I've tried locking the .EXE file with InterLoc from PACE but that dose no good sense skip over the .EXE file, I also tired locking some of the .DLL files

But that didn't work either sense File Maker uses its owned .DLL

I'm using InterLoc because I want to be able to supply my customers with a timed DEMO.

Any help would be AWASOME

I've racked my head on this one!!

Thanks Ron Bascom

---

Problem = Users can access solution with password from FMP.

Solution = Only give the users a password that allows them the basic use of the solution. DO NOT give them the master password.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Senior Filemaker Developer

http://www.database-resources.com

mailto:[email protected]

=-=-=-=-=-=-=-=-=-=-=-=-=

[printit]

Hi Kurt Knippel

Thank you for your fast response to my question.

However I don't think the answer is quite that simple.

We are only giving the password for a "low level entry" to the database.

So my problem is we don't want someone to be able to open the solution in File Maker.

I did Wright a script that runs when the runtime solution first opens, the script open's a blank data base that cannot be opened in my runtime solution, but can be opened in FM, if that data base is open it will shut down FM.

Here is the problem that I encountered when my solution opens I get a message that say

"This file cannot be opened because it dose not belong to this solution"

So I want to set some kind of error capture for this script that's say's ok if you don't belong to this project then do this.

I hope this makes some sense

Ron Bascom

[Kurt Knippel]

quote:

---

Originally posted by printit:

Hi Kurt Knippel

Thank you for your fast response to my question.

However I don't think the answer is quite that simple.

We are only giving the password for a "low level entry" to the database.

So my problem is we don't want someone to be able to open the solution in File Maker.

I did right a script that runs when the runtime solution first opens, the script open's a blank data base that cannot be opened in my runtime solution, but can be opened in FM, if that data base is open it will shut down FM.

Here is the problem that I encountered when my solution opens I get a message that say

"This file cannot be opened because it dose not belong to this solution"

So I want to set some kind of error capture for this script that's say's ok if you don't belong to this project then do this.

---

The files are all still Filemaker files and you cannot prevent them being opened in FMP. I am not even sure if you can tell if they are being opened via FMP or the Runtime.

Make sure to Set Error Capture on in your scripts, this will supress many of the error messages, but not all.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Senior Filemaker Developer

http://www.database-resources.com

mailto:[email protected]

=-=-=-=-=-=-=-=-=-=-=-=-=