Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
Error when upgrading DBISAM tables from 3.27 to 4.29 |
Fri, Apr 16 2010 11:32 AM | Permanent Link |
Paul Chandler | Note: This error only occurs when attempting to upgrade a 3.27 table from my Windows 7 Pro machine. The upgrade works fine from XP Pro.
On the Win 7 machine I get this error when attempting a table upgrade: DBISAM Engine Error #11013 Access denied to table or backkup file 'C:\program Files\DBISAM Additional\Version 4\utils\dbsys\59640.dat This sort of looks like a Windows security issue, but I don't see how that can be. I have local Admin rights on the machine and I'm also a Domain Administrator on the network. I need to upgrade dozens of tables so I can upgrade various Delphi 7 apps to Delphi 2010. It would save time if I could perform the table upgrades on my new machine instead of having to use my old one. Any suggestions would be gladly appreciated. |
Fri, Apr 16 2010 11:38 AM | Permanent Link |
Raul Team Elevate | It looks like a permissions or virtualization issue as dbsys can't create or access temporary tables. Are there any numeric dat files in that folder (e.g. 59640.dat).
In dbsys options there should be a private dir path - change it to something you know for sure you can write to and where Win7 does not try to virtualize access (e.g. c:\temp or location of your db files) and try again Raul |
Fri, Apr 16 2010 12:20 PM | Permanent Link |
Paul Chandler | All fixed, Raul. You rock! Your suggestion got me thinking. Of course this is a permissions issue, and Win 7's security is more stringent. Although I effectively have all kinds of access permission, for some reason that didn't translate to the dbsys folder. So what I did was give myself explicit access to the dbsys folder and that did the trick.
Thanks for the help. Paul Raul wrote: It looks like a permissions or virtualization issue as dbsys can't create or access temporary tables. Are there any numeric dat files in that folder (e.g. 59640.dat). In dbsys options there should be a private dir path - change it to something you know for sure you can write to and where Win7 does not try to virtualize access (e.g. c:\temp or location of your db files) and try again Raul |
Sat, Apr 17 2010 6:26 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Paul,
<< All fixed, Raul. You rock! Your suggestion got me thinking. Of course this is a permissions issue, and Win 7's security is more stringent. Although I effectively have all kinds of access permission, for some reason that didn't translate to the dbsys folder. So what I did was give myself explicit access to the dbsys folder and that did the trick. >> An easier alternative is to change the Private Directory in DBSYS (File/Options) to the user-specific temporary files folder under Windows 7: C:\Users\<UserName>\AppData\Local\Temp -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |