Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 8 of 8 total |
Temporary Data Table Extension |
Wed, Aug 23 2006 10:31 AM | Permanent Link |
Michael Binette | I want to change the file extension of the temporary data tables to
avoid AV issues. I know you can change it by setting Engine.TableDataTempExtension := '.tmp' and you can get DbSys.exe to use the new extension by editing the DbSys.ini. My question is about client-server. Does setting the TableDataTempExtension property on the client from within my application tell the server to use the new extension or do I have to change something in the server as well. Right now i am simply using the standard dbsrvr.exe as my server. -- Thanks, Michael Binette |
Wed, Aug 23 2006 10:36 AM | Permanent Link |
Jason Lee | In C/S there shouldn't be any tables saved on the client computer. You
will need to change the server's extension property to make it like that on the server. Michael Binette wrote: > I want to change the file extension of the temporary data tables to > avoid AV issues. I know you can change it by setting > Engine.TableDataTempExtension := '.tmp' and you can get DbSys.exe to use > the new extension by editing the DbSys.ini. > > My question is about client-server. Does setting the > TableDataTempExtension property on the client from within my application > tell the server to use the new extension or do I have to change > something in the server as well. Right now i am simply using the > standard dbsrvr.exe as my server. > > -- > Thanks, > Michael Binette |
Wed, Aug 23 2006 12:03 PM | Permanent Link |
"Jose Eduardo Helminsky" | Michael Binette
> My question is about client-server. Does setting the > TableDataTempExtension property on the client from within my application In C/S does not matter if the clients were running AV. What it relevant is the server. If you don´t install AV in the server (my suggestion) then there is no problems with AV. Database server should run isolated if possible. Eduardo |
Wed, Aug 23 2006 12:26 PM | Permanent Link |
Michael Binette | I totally agree that it should be run isolated but our customer base
tends to dedicate the "most powerful" client machine as the server meaning they use it for other things like Email at the same time. Not our recommended setup but unavoidable. > > In C/S does not matter if the clients were running AV. What it > relevant is the server. If you don´t install AV in the server (my > suggestion) then there is no problems with AV. Database server should > run isolated if possible. > > Eduardo |
Wed, Aug 23 2006 3:07 PM | Permanent Link |
"Jose Eduardo Helminsky" | Michael
I understand your point. My suggestion then is disable DAT, BLB and IDX extension in the AV software only in the server machine. Eduardo |
Wed, Aug 23 2006 3:30 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< My question is about client-server. Does setting the TableDataTempExtension property on the client from within my application tell the server to use the new extension or do I have to change something in the server as well. Right now i am simply using the standard dbsrvr.exe as my server. >> You'll have to modify the dbsrvr.dpr project that comes with DBISAM (\servers\dbsrvr subdirectory) so that it uses a different temporary table extension. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Jun 28 2007 6:01 PM | Permanent Link |
Steve Barker | Hi Tim,
Would it be possible sometime to alter the default source to dbsrvr to enable file extension changes to come from the ini file (as dbsys does)? i.e. add the following lines (plus others if required) to line 341 in main.pas of dbsrvr: ServerEngine.TableDataExtension:=ReadString(PARAMS_SECTION,'Table Data Extension',ServerEngine.TableDataExtension); ServerEngine.TableDataTempExtension:=ReadString(PARAMS_SECTION,'Temp Table Data Extension',ServerEngine.TableDataTempExtension); Would save me recompiling when new versions are released. I change the .dat file extension for 2 reasons: Some clients have AV on the server which deletes .dat files when you least expect it, and also it helps me separate versions 3 and 4 of dbisam and file associations with dbsys. I still have many legacy apps using ver 3, so I use .db4 extensions for ver 4. thanks, Steve "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote: Michael, << My question is about client-server. Does setting the TableDataTempExtension property on the client from within my application tell the server to use the new extension or do I have to change something in the server as well. Right now i am simply using the standard dbsrvr.exe as my server. >> You'll have to modify the dbsrvr.dpr project that comes with DBISAM (\servers\dbsrvr subdirectory) so that it uses a different temporary table extension. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Jun 29 2007 1:37 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Steve,
<< Would it be possible sometime to alter the default source to dbsrvr to enable file extension changes to come from the ini file (as dbsys does)? >> Sure, I'll see what I can do. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |