> > >
> > > Dear all Experts.
> > >
> > > Today I run Foxbase Exe, I noticed following objects.
> > >
> > > I software all of the dbfs were available and working fine.
> > >
> > > When I quit the software I observed followings about dbfs. I doubled clicked any dbf it showed "Not a dbf file"
> > >
> > > After this I executed the software many times and worked well.
> > >
> > > Conculusion:
> > > May there is some procedure to corrupt dbf on quiting time and when softare runs then all dbf's are repaired.
> > >
> > > In my point of view, this is a good idea to protect dbf opening without software even in Windows Explorer.
> > >
> > > If someone needs that FoxBase Exe I can send for more enhancment.
> > >
> > > Wish to have good dbf securing procedure.
> >
> > Are you saying that you can open vfpN files with a foxBASE app????
> > I can hardly imagine that.
> >
> >
> >
> > Boudewijn Lutge®ink
> > The attitude of "An eye for an eye and a tooth for a tooth" will make this world toothless and blind (Gandhi)
>
> Dear Sir,
>
> I am talking about Foxbase own dbf files.
>
> thanks

Tariq,

As I explained in my email to you, this is not a very secure method of "securing" your data. Take a look at the SET COMPATIBLE FOXPLUS command in help. If I have VFP, I can browse a FoxPlus table without any problems.

If your intent is to secure the database in a LAN environment, begin by removing VFP from any of your user's machines. The only people in your organization who should have access to VFP are the development team. Create and run an install procedure that will install the VFP runtime libraries (and any other dll's that you use) on the user's workstations. You can do this with Install Shield Express or with Inno Setup. Install Shield Express ships with VFP and Inno is a free download. When you have done this, your users will not be able to double click on a .DBF file and have it open in a browse window.

Now, get together with your SysAdmin. Your SysAdmin can use Active Directory to set permissions on files and folders. Your users should only have read/write/execute permissions to your EXE and the data. (The SysAdmin can set these permissions for you.) If you want to, you can refine security even more by designing your app with Active Directory in mind. For example, let's say that you have an accounting app that includes a payroll utility. If you were designing this with AD in mind, you would make the payroll portion of your app a seperate EXE. Your SysAdmin would then create a PayrollDept user group and that user group permission to read/execute your Payroll.EXE file.

Ken
You shall know the truth - and the truth shall set you free. (John 8:33)