Lennart, we use Windows XP. I have limited the rights for all users, but the files are on our server and there's always more than one person that has access to all files on the server. I think I give Brian's idea with the run time a go.
Thanks to all. Gerard 2009/1/27 Brian Hancock <[email protected]> > You can still create a run time version, but I am not sure it would help > in this case.. > > > > DP /RUN > > > > It will ask you for the name of the STR and also name of DP.SYS > > The /RUN will create a new Runtime executable DPR.EXE which will have the > STR and the name of the DP.SYS options bound to it. > > > > This only stops people from getting to definer mode and so they cannot > change the core program but it still allows access to reports, etc. > > > > However you might like to try various means including the DPR to obfuscate > the launching of the program, for example > > > > Copy DP.SYS to a new filename perhaps make it a little obscure such as > tutorial.sys > > Create the run time as describe above but specify you new dp.sys as say > tutorial.sys > > Copy the DPR.exe to a folder where the user has limited rights. Copy the > move the tutorial.sys file to that folder. > > Start DPR with a full path (in DOS format) to where the STR is located > > Eg DPR f:\Company\apps\MyApps.str > > In the data folder delete the DP.EXE and DP.SYS > > > > Of source you do not need to use the DPR for this, you can keep the normal > executable in a different folder anyway, but at least with the DPR you do > not get to see which folder the data is located in, and keeps other logic > and access to panels a little more secure > > > > If you do not already have passwords you can user DPR with > /U-userid:password switch eg /u-bjh:@Q#W, in the shortcut so they do not > necessarily know that they have a login name > > > > Another alternative is you might be able to create a username and password > from a server login script using an environmental variable eg SET dpun=bjh > and SET dp...@q#w (or even use an existing variable) and then in the > launcher use DPR f:\Company\apps\MyApp.str /U-%dpun%:%dppw% This would then > log the user into the DP application without them even knowing about the > login. > > > > If you wanted to obfuscate even further you could use a batch file compiler > to put all the commands and arguments necessary to run the program into one > executable. > > > > Brian > > > > > ------------------------------ > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *P.Boekestijn > *Sent:* Tuesday, 27 January 2009 7:17 AM > *To:* 'Dataperfect Users Discussion Group' > *Subject:* RE: [Dataperf] Security > > > > Hi Gerard, good question, I'm having the same just coming up by having > terminal session from several sites into one server / directory. > > > > In the old days (1994?) there was a runtime version available. Not sure > this is still possible. > > > > I hope to get a workable answer from the group. > > > > Kind regards, > > > > Met vriendelijke groet, > > > > *Peter Boekestijn* > > > > -----Oorspronkelijk bericht----- > *Van:* [email protected] [mailto: > [email protected]] *Namens *Gerard van Loenhout > *Verzonden:* maandag 26 januari 2009 20:36 > *Aan:* Dataperfect Users Discussion Group > *Onderwerp:* [Dataperf] Security > > > > Question for all. > > > > How do I secure my DP files? They're all in one directory on the server. > > It's easy for someone to copy the files and have them at home. > > The passwords are fine, but when someone leaves the company they can still > access the database at home. > > > > Is there a way to hide the STR, IND or TXX file so no one can copy the > whole enchilada? > > Or spread some files over other directories? > > > > Regards > > Gerard van Loenhout > > > > _______________________________________________ > Dataperf mailing list > [email protected] > http://lists.dataperfect.nl/mailman/listinfo/dataperf > >
_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
