Hi,
I have a strange problem with DBISAM 4.32 (delphi XP2) and data on shared
network drive; There is a Windows 7 64 bit SP1. From application, connect
with  data on other servers works (XP, W7) but when connect with data on
this PC, there is a refresh problem.
Every record update from a client is not visible to other users. I must
disconnect the application and reconnect for see update or appended.
Only on this machine.
What Do you think? There is a problem on W7? Workaround?
Thanks in advance
Stefano Monterisi

Stefano,

<< Every record update from a client is not visible to other users. I must
disconnect the application and reconnect for see update or appended. Only on
this machine. >>

Can the W7 64-bit machine see updates from other users ?  Or is it only the
updates on the W7 machine that aren't visible to other users ?

It sounds like an SMB bug, but I haven't personally seen any such bugs with
W7.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

<< It sounds like an SMB bug, but I haven't personally seen any such bugs with
W7. >>

FWIW, we're beginning to see a number of customers experiencing table corruptions, involving W7 and 2008 server, usually virtualised, though that's probably a red herring.

Charles,

<< FWIW, we're beginning to see a number of customers experiencing table
corruptions, involving W7 and 2008 server, usually virtualised, though
that's probably a red herring. >>

Is this with a file-sharing setup, as opposed to using the DBISAM Database
Server ?

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:


<<Charles,

Is this with a file-sharing setup, as opposed to using the DBISAM Database
Server ? >>

Tim, sorry just seen this, rather late...

It was file sharing and the problem "went away". The customer's network is being supported by a third party outfit, who after some months, did something; we don't know know what; and the problem "went away". Allegedly, all they did was create a new share on the server and asked us to "reinstall the application". We simply copied the entire system from old share to new. We suspect the "reinstall" request was to try to pin the problem on our application once they had discovered the cause (4 months down the line).

Frustratingly, we don't know what really was the cause or the resolution, as we now have *exactly* the same problem started at another site, after they started adding Windows 7 machines to the otherwise Windows XP client network. I have yet to confirm more details, having just returned from my annual holiday.