xHarbour ADS problem

[TimStone]

I realize this is off topic for FWH but I would appreciate any ideas from the experts who use Advantage Database Server

This problem occurs at only one install. Everywhere else that ADS exists, it runs fine.

A client wanted to test this product to see if there was a performance improvement for his client machines. We installed it on a Windows XP Pro machine for testing purposes. This is where the data files reside.

All of the machines are set to start in Client Server mode. If the server is not found, the program will not start. On all of the workstations, they start in this mode and when we check inside the program for the type of server, it registers as Client Server.

The Client program installed on the "server" is also set to start only in Client Server mode. However, once inside the program, when we check the type of server it shows LOCAL server, and when other machines try to access files, they can't if this client has them open.

This is the only location where this occurs.

I am using xHarbour with ADSCDX.

If anyone has thoughts on where I can look it would be appreciated.

Tim

[arpipeline]

Tim,

Please confirm this for me:

1) LAN Server hosts ADS and client Exe

2) Multiple workstations run the Exe "across" the network.

4) All but one are running in Remote server mode

5) The one not running in Remote server mode shouldn't even start up

6) Regardless of Local Server or Remote Server modes, you are puzzled why a Local server user would "block" the remote server users

Andy

[TimStone]

All of these are correct except I know the one running in LOCAL mode would be expected to create a problem.

The one that starts in LOCAL mode is physically on the server. It is told to start an client server mode, and apparently it does because it passes an immediate test, but then it switches to LOCAL.

I have many installations just like this that work perfectly. I would expect this must have something to do with a windows setting on the server, but I don't know what. It is ADS 8.1

[arpipeline]

Tim,

I'm not sure why you would expect it to create a problem, unless:

1) The "local" system is using a different locking scheme, or;

2) The "local" system is using the tables EXCLUSIVEly

At any rate, it *does* sound like Windows (firewall?) is blocking remote access. How are you USEing the tables? I remember seeing somewhere ADS AUTOUSE functions that default to LOCAL mode if REMOTE mode is unavailable. Does that sound like a possibility? The USE *should* fail unless there is some code defaulting to LOCAL use.