Hello mrjoltcola.... I'm nto sure what you mean by conneting via the network instead of through a share. The folder that the DB file is in needs to be shared to get to it over the network.
Main Topics
Browse All TopicsI am trying to connect to an SQL Anywhere 10 database that is on a Windows 2003 standard server in an Active Directory structure from my computer. If I use the drive mapping that is on my local computer along with the path to the database file (ex: R:\xxxx\yyyy ) I get a database not found error. If I replace this with the full path of the server using the hidden drive (ex: \\sqlserver\e$\data\xxxx\y
Thank you,
Steve
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>>The folder that the DB file is in needs to be shared to get to it over the network.
Yes, that is because you are opening the actual SQLAnywhere db file directly with Sybase Central or other tool. Thats not the best way to do it over a network, mainly because it prohibits multiple people accessing the DB at the same time.
You can setup an Adaptive SQLAnywhere Server to run on the server itself, it will handle network connections from any SQLAnywhere client without a need for physical access to the .db file. This is the better way to accomplish what you are doing. A remote connection really does not need direct access to the file.
An ODBC / DSN connector for SQL Anywhere can connect locally or over a network. The DSN is different, and includes IP address, port, etc. but it works. I use it to run SQL Anywhere on Linux and access from Windows boxes. But again, since I do not know the answer to your initial question, and it does not sound like you want to config SQLAnywhere as a db server, I'll have to leave the question for someone else.
The server is all set and running. The issue is that the ODBC connector requires the database file location and when I use the share location it tells me that the file is not found but when I use the full path with the hidden system drive letter then it works like a charm. Very puzzling. But thank you anyway for your assistance.
I still suggest you talk to your vendor about this. It is an uncommon way to mount SQL Anywhere databases. I personally would never do it that way in any of my products. The server engine is completely capable of network client support without the need of direct access to the db file. If the vendor has recommended this I would want to know why. Good luck.
Business Accounts
Answer for Membership
by: mrjoltcolaPosted on 2009-07-24 at 10:42:24ID: 24937214
I don't know the answer to the fileshare question, but I am curious if you can simply start an ASA server on the Windows 2003 server and connect via the network instead of directly mounting the database through a share. Reason is, you will have issues if someone else tries to do the same. Is this not an option?