Sergey

The candidate record has around 800-900 fields, which I have split across several tables within SQL Server, ie Candidate, CandidateQualifications, CandidateCriteria, CandidateHistory etc. When I want to modify the candidate record I'm using SQLExec to select the relevant records (using CandidateID) from these tables, and I then set myObject.datasource to the relevant field. When I wish to update the remote SQL Server record, I'm using SQLCommit, or should I require, I can rollback the changes.

Obviously, as there is no native date-only format in SQL Server the above commits/rollbacks will require some additional processing to convert date formats backwards and forwards.

Why would I need to change to CA, other than to get around the 254 field limit (which isn't an issue as my Candidate tables are specifically less than 254 fields)?

At the end of the day, I just want the easiest solution. I can still modify the SQL Server tables if need be, but if I do change the data access layer I would have to do it now.

Regards