client connection sqlanywhere databse

my sqlanywhere databse is on the server,i connect to databse by running the dbeng50.exe on the client machine  with the path of the network of the databse server it get started and then i run my client with the path of the server is it necessary to start dbeng50.exe  on every client machine before making the connection before running the client

after running the client on the first machine when i start my dbeng50.exe on second client machine with the path of the server then it gives error message "could not open/read databse file " and the path and name of the server databse

if i close my client on first machine then client gets started on second machine after starting the dbeng50.exe with the server path

its very urgent so plase help me out
lavAsked:
Who is Participating?
 
dapperryConnect With a Mentor Commented:
You have this set up all wrong.  You don't want to be running dbeng50.exe, unless you are running a database purely locally.  You want to set up a server service on the machine with the SQL Anywhere Server set up on it.  You do this put setting up an entry in SQL Anywhere Service Manager, then clicking 'New' and then clicking on the 'Network Server' radio button, and clicking on 'Ok'.  You then fill out the next dialog box, by giving the new service a name, by giving out any parameters, and by selecting whether you want this service to be started automatically (I'd reccommend it, so you don't need to be logged on to the Server to have the service running)  You will note that the service executable is actually DBSRV50.exe.  If you run the program interactly with a ? mark you can get a list of parameters to put in the parameter box.  Heres an example parameter entry for the 'testme' service:

-x ipx
-c 50M
 c:\test\test.db

The first line specifies which network protocols you want to use, the 2nd, how much of a memory cache you want, and the 3rd is the path & filename of the database.

Anyhow, then you install the client on your other workstations.  AFter that you run "dbclient.exe -x ipx testme" from the workstation, and you are then connected.  You could also probably set up some kind of a startup program to launch the client each time a person logs in, but whatever...

Hope this helps

:) D Perry
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.