An updated ODBC driver is now available on the downloads page:

http://www.lantica.com/Support/downloads.html

If you have previously installed the Sesame ODBC driver, you must delete any existing sesodbc.dll files from your system before installing the update. On a Windows 2000 system, this file will be in the C:\WINNT\system32 directory.

Thanks for new file Mark.

Suggest updating the download page to show the ODBC latest version. 

Without knowing about this forum message, a user going to that page would not know that the ODBC is now a new version, the page only references the current Sesame version. 

Will a change log also be created for ODBC? Sample result is shown here:

Current Sesame ODBC Version: v?.? ? ? ?
Release Date: Feb 03, 2004
View Change Log

Thanks again.....

Quick update.....ODBC 1.0.1 still not working in Access or Word.  Both apps get hung up trying to make the connection.

Removed old dll before installation (7/04/00), left over from some beta testing?.  But that was after installation of ODBC version 1.0.0 

Installed ODBC version 1.0.1  Date of newly installed dll was same date as old dll (7/04/00) that was removed! 

Manually copied new dll (1/27/04) from Setup32 folder to Windows\System folder on WIN98SE system. 

Checked date of dll in version 1.0.0 and saw that it was
12/10/03, which is not what was removed manually. 7/04/00 was removed, so 12/10/03 was not installed?

It appears that the installation is not actually installing the dll into the \Windows\System folder.  Both versions 1.0.0 and 1.0.1 seem to be installing sesodbc.dll with the date of 7/04/00.  I am not believing what I am seeing.

Just another observarion: both version 1.0.0 and 1.0.1 dll files have same internal version reference, though dates are different.  File sizes of both versions are also identical, = 1,015,808.  That might be okay, but since this was to correct some problems I thought that perhaps the size would change, and that the internal version would also change.

So I now have three non working versions of sesodbc.dll:
07/04/00, internal version  1.00.0000, 1,015,808 bytes, Version ?.?.?
12/10/03, internal version  1.00.0000, 1,015,808 bytes, Version 1.0.0
01/27/04, internal version  1.00.0000, 1,015,808 bytes, Version 1.0.1

So we will have to wait for Version 1.0.2 next?

Leaving right now, but quick answer is per the Sesame documentation.  Merging with Samples Customers.db.
Merge using Ascii file is fine.  ODBC is failing.

Selecting MS Query at point of Get Data.
After selecting Sesame Customers DNS, the MS Query screen just shows hourglass.  Need to do STL-ALT-DEL to get Close window which shows MS Query not responding.  Word Document is then frozen and Word also needs to be forced closed

Have tried using server name with and without \\.
Have tried with Sesame Server.
Have tried with Stand alone Sesame

Using Word 2000 with WIN98ME. 

Will be back tonight, good luck......

Thanks for this major clue Mark.  
Quote:
This did it for me.   Forced me to take a microscopic look at my settings.  Needed adjustments.

PROBLEM to be addressed: There are a number of references in the UserGuide on pages 417-419 that need to be corrected.  Most noticeable is the missing hyphen in front of server/client.

My server shortcut had omitted the port since it was listed as optional, the default being 20000.  I had to add :20000:20001 to finally make the connection.  That along with the hyphens resulted in success.  

And on those pages it also looks like there is a space between machine name and the :port:port, but no space should be there.
===============================
Success history is documented here:

1.  Doing Word Merge worked fine, had options to filter and/or sort records before merging.  The best part of the ODBC was not having to make an export file.  And I can use the normal Word field formatting tools to clean up appearances as needed.

2.  Using Access was another issue, finally resulting in success.  Here are some abbreviated notes to save others from some of the steps I went through:

1.  Made a Pass Through query, got error message:  
Quote:

=============================
2.  Made a new standard query based on the Pass Through query, got this similar error message when adding the Pass Through to the Design Grid:  
Quote:

=============================
3.  Tried File, External Date, Link Tables, saw one table=Customers, OK.  Result=linked table named Customers.    Opening table got error message:  
Quote:
 
followed by another message: 
Quote:
 
=============================
4.  Made a new query based on the Linked table Customers.  Allowed me to see all fields.  
And I can do sorting, filtering criteria, formatting, user prompts, use VBA, combine with data from other applications, etc.  THAT's WHAT I WANT!
=============================
Solution is to make a table using a link to Sesame, then making a query based on that table.  Now all forms and reports can be made from that query.

Additional observations:  All testing was done on WIN98ME with Access/Word 2000.  All work was done on local machine, not using Server-Client across a network, but the ODBC Sesame database object was on another workstation across the Windows Network.

Was unable to write back to update fields from Access to Sesame, but not surprised.  Would have been more surprised if I could.

So......ODBC version 1.0.2 is probably not needed?  Still curious about the installation of the old file, but will do tests on other systems to try to duplicate that again.

Access and Word cannot make the ODBC connection to Sesame if Sesame is running by itself as a stand-alone server-client combination.  You must have the Server running.  If you also have a Client open, then no connection can be made.  This is because of no license for multiple users.

Based on the experience with no connection when Client was running, I suspect that I will have the same problem if I have multiple DSNs to call at the same time.  More testing on that over the weekend probably.  

It would look like multiple licenses will be needed to open more than one Sesame application at the same time.  This really reduces the ability to merge databases together in queries combining information from more than one source.  An extra license for every source to be combined is too prohibitive.....hope there can be a cheaper solution to that.  At least allow a single workstation to make multiple connections with a single license.  Multiple connections to the same application could still be restricted by licensing.

But at least this ODBC is now working so I can move ahead to combine Sesame data with QuickBooks and other applications.

Thanks again........  

Quote:

Done.  Thanks again....