Importing via ODBC to MS SQL produces 5 records

[maverik_uk]

As a relative newbie to the world of ESS and ODBC, something has got me flummoxed!

When I do an import of a Stored Procedure via ODBC to MS SQL from table with 1 record, FileMaker produces 5 records in my SQL table.

The MS SQL staff are happy to resolve it their end but they are finding it too amusing for comfort! : Is there a reason why this happens and more importantly how can I resolve it?

[mr_vodka]

Without knowing more information about your stored procedure or SQL statements, its hard to help.

So far from what I can tell, I believe you are stating that you have the Datadirect SQLLink driver and you are importing FileMaker data into the MS SQL table correct?

[maverik_uk]

I am testing on Mac OSX Leopard using FMPro v9.0.3 although I have encountered the problem on Windows XP client. I am using the Actual Technologies driver for MS SQL. I am in dialogue with Actual although in early stages.

From an FM table of 1 record, I do an import script using a stored procedure via ODBC. The stored procedure is designed to create that very same 1 record in the MS SQL table and give me a response back to say the transaction is OK, thus the use of an import. The aim is for the contents of the FM and SQL table to be the same.

If there was 5 records in the FM table or SQL table, I would understand - regardless I still end up with 5 SQL records all created within a millisecond of each other. If I go through the process manually from the File:Import menu, I get the same.

Like I say, I can dedupe from the SQL side OK but it shouldn't be this way?

[bcooney]

You're not is some sort of demo mode are you?

[Garry Claridge]

Sounds like a Trial version to me also!

Good Luck.

Garry