Hi Folks,
Just trying to get some feedback as to whether people out there have issues with the database linking.
I've got 3 sites all linking to 1 SQL 2005 database (different tables within same DB) This worked fine under V9, but i've never managed to get it to work under V10.
If i create a new site in V10, i can connect to the external datasource no problem. I can map fields and the data appears in catalog. However if I close actinic & go back in, going to the external database screen just gives an error - odbc connection to <tablename> failed.
If i try to re-link to the tables, it gives me the list of tables in the DB, but then gives the odbc connection failed message again.
I've tried setting database compatability to SQL 2000, but that doesnt help. I've tried installing the SQL 2005 on my local machine, but I still get the error.
I've had a case open with Actinic since May, but no resolution yet.
As a workaround, i've exported the tables to a ms access database, and they link ok. I've got 2 issues with that - firstly it makes updating the tables awkward, and secondly I paid extra for business plus to get the SQL linking!
Client is XP or Windows 7, both have the same issue.
Am I the only one?
Ross.
Just trying to get some feedback as to whether people out there have issues with the database linking.
I've got 3 sites all linking to 1 SQL 2005 database (different tables within same DB) This worked fine under V9, but i've never managed to get it to work under V10.
If i create a new site in V10, i can connect to the external datasource no problem. I can map fields and the data appears in catalog. However if I close actinic & go back in, going to the external database screen just gives an error - odbc connection to <tablename> failed.
If i try to re-link to the tables, it gives me the list of tables in the DB, but then gives the odbc connection failed message again.
I've tried setting database compatability to SQL 2000, but that doesnt help. I've tried installing the SQL 2005 on my local machine, but I still get the error.
I've had a case open with Actinic since May, but no resolution yet.
As a workaround, i've exported the tables to a ms access database, and they link ok. I've got 2 issues with that - firstly it makes updating the tables awkward, and secondly I paid extra for business plus to get the SQL linking!
Client is XP or Windows 7, both have the same issue.
Am I the only one?
Ross.
Comment