Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 8 of 8 total |
LargeFileSupport |
Wed, Jul 17 2013 9:31 AM | Permanent Link |
Darren | I have been seeing corruption at one site and I want to verify that all apps that touch the data have LargeFileSupport turned on. Would removing the if FLargeFileSupport line and the else from the dbisamen unit be all I need to do to force all of my compiled applications to be the same and use the larger file size?
I would have to recompile the dbisam server as well, but would, could this bite me somewhere else? I have the dbsrvr.ini with the setting turned on but had a user hit the "table is too large" error while supposedly connected to that server. 4.36b1 Thanks, Darren |
Thu, Jul 18 2013 4:37 AM | Permanent Link |
Fernando Dias Team Elevate | Darren,
You don't have to recompile DBISAM or the server at all. Just make sure that you have: 1. Large File Support set to 1 in dbsrvr.ini. 2. TDBISAMEngine.LargeFileSupport set to True in all your applications (Only needed if client applications can access the tables directly) 3. Large File Support set to 1 in dbsys.ini (Only needed if tables can be accessed directly using dbsys.) -- Fernando Dias [Team Elevate] |
Thu, Jul 18 2013 8:24 AM | Permanent Link |
Darren | Thanks. I am aware of those options and use them currently. I was just bit by a dbsrvr that was running with largefilesupport not on, even though the ini file had it set to be on. Turned out I think the ini file was placed there after the service was started. If I were to recompile them with it turned on, then I don't have to worry about ini files, registry entries, etc... This was a tough one to find and resulted in a lot of corruption over time.
|
Sun, Jul 21 2013 2:40 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Darren,
<< Thanks. I am aware of those options and use them currently. I was just bit by a dbsrvr that was running with largefilesupport not on, even though the ini file had it set to be on. Turned out I think the ini file was placed there after the service was started. If I were to recompile them with it turned on, then I don't have to worry about ini files, registry entries, etc... This was a tough one to find and resulted in a lot of corruption over time. >> I certainly wouldn't recommend changing the code instead of using these options. You'll have to keep putting your code changes back in from build to build, and from release to release, which is certainly more prone to issues than just making sure that the settings are correct for the dbsrvr.ini file. Tim Young Elevate Software www.elevatesoft.com |
Tue, Jul 23 2013 5:49 AM | Permanent Link |
Jose Eduardo Helminsky HPro Informatica | Tim and others
My vote for next DBISAM release is to turn LargeSupportFile to True by Default. It will need a compilation of all applications but we have never need to worry about anymore. |
Fri, Jul 26 2013 12:52 PM | Permanent Link |
Raul Team Elevate | This would be completely unacceptable.
You're introducing a major breaking change for very little benefit. Anyone using LargeFileSupport today would know they use it and to handle it properly. Raul Jose Eduardo Helminsky wrote: Tim and others My vote for next DBISAM release is to turn LargeSupportFile to True by Default. It will need a compilation of all applications but we have never need to worry about anymore. |
Mon, Jul 29 2013 6:22 AM | Permanent Link |
Jose Eduardo Helminsky HPro Informatica | <<
Raul wrote: This would be completely unacceptable. You're introducing a major breaking change for very little benefit. Anyone using LargeFileSupport today would know they use it and to handle it properly. >> I am sorry but I can´t see it in this way. The developers should do nothing about LargeFileSupport independent if this is True or False. This property only exists because Windows 98 (very old) support and now the file size, specially BLB files grows a lot if you save pictures or a lot of XML files (my case). I have one customer with 10Gb in just one BLB file. I am not intended to create problems to others developers because it is easy to set LargeFileSupport. Regards Eduardo |
Mon, Jul 29 2013 8:53 AM | Permanent Link |
Raul Team Elevate | What you are proposing means that we'd have to update every one of our apps and utilities and copies of dbsys to make sure this is disabled again (since every single copy of our apps and utilities currently out there has it disabled and it's too much work to make sure we can update them all). I'm simply saying that leave it as is - people who need largerfilesupport can enable it and they KNOW they need it enabled. Like you said it's easy to enable it so lets leave this setting as is. Raul On 7/29/2013 6:22 AM, Jose Eduardo Helminsky wrote: > I am not intended to create problems to others developers because it is easy to set LargeFileSupport. |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |