I am currently hooking my system on the ODBC connection Maximizer creates when it starts up, so it does not give me any options. How can I avoid the error the insert and update commands give when using MR/MS or even tried [MR/MS].

(Using ado instead of DAO)
Can anyone help?

Tobie

You need to be using a System DSN that employs the Maximizer ODBC driver, not the Pervasive driver. (Note that the MAP_AddressBookName DSNs use the Pervasive driver, so they're not what you want.)

When you establish your DSN that uses the Maximizer ODBC driver, click the "Options>>" button and you can select the MR_MS option to change the name of that column from [MR/MS] to [MR_MS]

I know what you mean.

The driver I am hooking into is a Maximizer ODBC driver. Say for instance the address book is called test, I specify the DSN name tmpMap_Test and it uses a System DSN created by Maximizer. This DSN is only temporary in nature, so it is not always seen in the Data Sources indow.

That is my problem- the driver is not permanent so that feature can not be set.

Thanks for your reply.

Tobie

Have you tried creating your own permanent System DSN for that Address Book in the ODBC control panel?

What I have done is update that field via the Pervasive ODBC driver. A bit more overhead, but it will do for now.

Tobie

If it gets the job done for you that's fine. However, bear in mind that you must use the Maximizer ODBC driver if you want MaxExchange to synchronize the changes.

Gord,

I thought I was told by support once that only changes entered through the application itself would be picked up by MaxExchange.

IIRC, this is because the MaxExchange tables are updated programatically, rather than at the database layer. Or something like that.

Hi, Jake.

That may have been true in the past, but I have been assured that the Maximizer ODBC driver for the current versions is "MaxExchange aware".