Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
DBISAM and WAN |
Thu, Jan 5 2006 8:57 PM | Permanent Link |
"Bern Rudisill" | Hello
I have a site using our application over a WAN using file sharing (I am still working on our C/S version of the app) The problem is this, I can copy the .dat and .idx files from the server to the worksation fine, but if I try and copy the files back up to the server I get an error, basically I either get a "Delayed write error" or a "Network location is not longer available". What is weird is it only happens on the .dat and .idx files, if I copy any other type of file up it works fine. I even tried to rename the .dat and .idx files to a different extension like tablename.txt and get the same errors. I know this is not a DBISAM error put just wanted to know if anyone has seen anything like this going over a WAN. Our application use to be in VB using MDB files and that worked perfectly in the same locations using the same files. Thanks Bern -- |
Fri, Jan 6 2006 12:43 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bern,
<< The problem is this, I can copy the .dat and .idx files from the server to the worksation fine, but if I try and copy the files back up to the server I get an error, basically I either get a "Delayed write error" or a "Network location is not longer available". What is weird is it only happens on the .dat and .idx files, if I copy any other type of file up it works fine. I even tried to rename the .dat and .idx files to a different extension like tablename.txt and get the same errors. >> Perhaps it is the size of the files that makes the difference ? -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Jan 6 2006 5:11 PM | Permanent Link |
"Bern Rudisill" | Tim Young [Elevate Software] wrote:
> Bern, > > << The problem is this, I can copy the .dat and .idx files from the > server to the worksation fine, but if I try and copy the files back > up to the server I get an error, basically I either get a "Delayed > write error" or a "Network location is not longer available". What is > weird is it only happens on the .dat and .idx files, if I copy any > other type of file up it works fine. I even tried to rename the .dat > and .idx files to a different extension like tablename.txt and get > the same errors. >> > > Perhaps it is the size of the files that makes the difference ? Though about that, we actually found the problem, apperantly Windows uses port 445 for file sharing also. They had this port closed, what is weird is the fact that the VB app using MDB files across a folder share worked fine, but the delphi app using DBISAM using the same folder share has to have port 445 open. Any problem solved. Bern -- |
Mon, Jan 9 2006 11:16 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bern,
<< Though about that, we actually found the problem, apperantly Windows uses port 445 for file sharing also. They had this port closed, what is weird is the fact that the VB app using MDB files across a folder share worked fine, but the delphi app using DBISAM using the same folder share has to have port 445 open. >> I would assume that both would have the same requirement for shared tables. Perhaps the VB application is opening the database exclusively ? -- Tim Young Elevate Software www.elevatesoft.com |
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 |