Always remember to use the 32-bit odbcad32in the Sys WOW64 folder to configure a 32-bit ODBC driver on your 64-bit Windows Server.
In order to access the data in the Polyhedra database from SSIS we created a connection manager from the ODBC Data Provider. Net Source must be used in the Data Flow because OLE Sources do not recognize ODBC connection managers. Net Source due to the ODBC connectivity restriction but unable to use expressions to create the dynamic query required to pull the data.
I am using the 32-bit ODBC manager (C:\Windows\Sys WOW64\odbcad32.exe).
When I try to add or edit a Visual fox pro source I get the following error: I checked for C:\Windows\system32\and it does exist.
Edit: When I make a DSN-less connection using a table in SQL Server rather than a view, it is updatable in Access.
I would have guessed my problem has to do with views not having a unique ID, but I'm confused why a DSN connection can be updatable while DSN-less cannot.
But via VBA, it doesn't know the primary key, so the linked view is not updateable. Name Like "v_*" Then Idx Flds = Nz(DLookup("Index Fields", "t_Linked View PK", "View Name = '" & TD.
This interface will be familiar to users of the older Active X Data Objects (ADO) data access interface.With some ODBC drivers, executing a complex stored procedure may fail with an error similar to: "Cannot open a cursor on a stored procedure that has anything other than a single select statement in it". Also, some drivers don't support the optional row_number parameter in As always Microsoft is clueless...I've been trying to connect to an Access database on a W2K on the network (not a local file, but mapped on the V: drive), via ODBC.It's not because it's DSN-less, but because you created it via VBA.If you link the view via the Access GUI, it asks you for the primary key.