Linking Sage 2008 to access 2007

[gemma-the-husky]

i havent checked, but i still think it may be because when you set up the odbc link with the sage driver, you get different behaviour depending on whether or not you select a indexed field

other thing may also be that the field type is not quite what you think, and this causes some usage difference

 

[Petroc88]

Gemma - I've tried linking with ODBC both by selecting the primary key in the Sage Table and then again by not selecting any field in the Sage table. I have experimented with obvious text fields using both <> and NOT LIKE and I have tried using apparently numeric fields again with <> and NOT LIKE. Every test scenario I have tried works perfectly on all operators such as > or < or = or LIKE but none of the test scenarios work with <> or NOT LIKE. A contributor on the Sageforum site posted a simple query that he said worked fine for him which I copied into my system and it failed.

Henry

 

[gemma-the-husky]

strange - are you using an older sage driver - perhaps that might make a difference - they change the odbc driver with each sage release

 

[Petroc88]

I ran the ODBC reinstall when I first started looking into the problem. I have just checked the driver version on this machine and on the server and they are both the same so I presume they are the versions shipped with this version of Sage (14.01.21.241).

The ODBC version is given as 2.00.00.609

FYI I have tested this with Sage data stored on the PC as well as with data stored on the server and the error is the same.