Hello RAC,

In screenshot NoTables.jpg it appears that you are also running another copy of Sesame besides the Sesame Server. Is this Copy of Sesame set up to be a Client? If it is, Have you tried connecting Access without that other client running(So connection count is 0 of 1)?

-Ray

r.a.colunga wrote on May 30^th, 2008 at 4:34pm:


Yes, you will be able to.

Quote:


They can connect in any order you want them to, there can only just be six of them.

-Ray

Just an FYI. one of the new features in 2.0 is that the ODBC client does not take up a normal client license. If you were running version 2, you would be able to connect 6 Sesame clients plus the Access client.

-Ray

I have run into a new problem linking Access up Sesame.  My office is running the Sesame server on a stand-alone server that is running Windows NT Server 2003 service pack 2.   The linking process works fine if I run the Sesame server and Sesame database on my local drive C but not off the office sever on drive G. My computer does have access to the G drive it is mapped.  The process I used was basically the same. The only change was to the ODBC Data Administrator driver I reconfigured it to Data = G:\Sesame\Data\Orders2.db, Host  = ntserver.  This process did not work what am I doing wrong.

Thanks,

The path to the DB file should be the path to the DB as if you were on the computer ntserver itself.

So if Orders2.db is stored in C:\Sesame\Data on the Server Computer ntserver. Then the filepath in the ODBC setup would still be C:\Sesame\Data\Orders2.db

-Ray

You do not need to include the Path to the Server by using a UNC path. The way the ODBC driver, and Sesame works, is that you don't need to include a path to the Server at all in the Database name. The Database path is pathed as if you were sitting on the Server computer where Sesame server resides.

Here's a quick Run Down of how the ODBC connection to a Sesame Server works
The ODBC Client runs
It connects to the Computer specified in the Host field of the ODBC setup on the Ports specified in the Port field of the ODBC setup.
Once connected it asks the Sesame Server to load the file named in the Database field of the ODBC setup.
The Sesame Server loads that file and hands back the list of Tables to the OBDC Client(Assuming the file exists and could be loaded)
The ODBC client can then tell the Sesame Server what Tables it wants and the Sesame Server returns the Data to the ODBC client.


Things to check(In Order):
Check that you can connect a normal Sesame client to ntserver:20020:20021
Check that you can open the Orders2.db file from the Sesame Client.
Once you have that file loaded note the Path that is shown on the top of the Sesame window. That is the path that you will want to use in the Database field in the ODBC setup.


Let me know if any of the things above gives you an error as that will give us a place to look for the problem.
-Ray

Hello Amor,

Can you e-mail your DB and DAT files to support@lantica.com so that we can have a look at them and see what is causing that error message.

-Ray