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

--

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

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

--

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