Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Paradox 10 Permissions 1

Status
Not open for further replies.

Duggsie

Programmer
Mar 2, 2004
3
AU
Hi,

I am installing Paradox 10 on an XP machine in a locked down environment. At runtime, the application seems to require write permissions to the root of C:\ in order to install a nyumber of .tmp files. If it does not have this access it produces errors associated with the CdrConv.exe installed by the application and does not function correctly.

Unfortunately, due to the policies applied to our workstations normal users do not have Write permissions to the root of C:\.

Has anyone else experienced this problem? Can anyone point me in the right direction with regards this issue?

Any suggestions are much appreciated.

Thanks,

Duggsie.
 
The default location for the Paradox .NET file is the root of the install drive (usually C:\). You can change that using the BDEAdmin program in the Borland folder. Click the configuation tab and look under Drivers->Native->Paradox and change the net file location to one where you have permission.

Mac :)

"There are only 10 kinds of people in this world... those who understand binary and those who don't"

langley_mckelvy@cd4.co.harris.tx.us
 
Thanks for your reply Mac.

Unfortunately, it doesn't really help me. I am aware that the default location for the .net file is the root of C:\ and I have redirected this to a location on the target machine where our users have full control.

My issue is that the application installs .tmp files on the root of C:\ at runtime and deletes them shortly thereafter. I do not understand why it neeeds to do this but it does it anyway. As soon as I give normal users full control of the C:\ drive the application works perfectly. The bad news is that once the application is deployed to our live environment the policies kick in and Users do not have this sort of control.

Thanks for taking the time to answer my post anyway. I appreciate it.

Regards,

Duggsie.
 
That's odd. The only other suggestion I have is to open the alias manager and look to see if any of the aliases point to the root directory and change them.

Mac :)

"There are only 10 kinds of people in this world... those who understand binary and those who don't"

langley_mckelvy@cd4.co.harris.tx.us
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top