UniDAC - Moving from MS Access to different Database
Posted: Wed 26 Oct 2011 16:32
Hi
BDS 2006
ADO & MS Access
Currently we are in the process of planning the move from MS Access to an alternative database, such as SQL Server 2008, when I stumbled upon the UniDAC VCL components and so thought I would ask whether anyone else had already been through this process using UniDAC and whether you would be willing to share your experiences.
We currently connecting to MS Access using ADO and so I would be interested as to how simple it would be to replace the TADOConnection, TADOCommand, TADODataSet and TADOQuery components with the equivalent UniDAC Components ?
My other area of concern is the SQL Syntax (which obviously is currently MS Access based and so uses none standard syntax such as IIF()). So I am interested in how the 'Unified SQL for writing server-independent queries' capability works and whether this would save us any time ?
Thanks in advance.
Stuart
BDS 2006
ADO & MS Access
Currently we are in the process of planning the move from MS Access to an alternative database, such as SQL Server 2008, when I stumbled upon the UniDAC VCL components and so thought I would ask whether anyone else had already been through this process using UniDAC and whether you would be willing to share your experiences.
We currently connecting to MS Access using ADO and so I would be interested as to how simple it would be to replace the TADOConnection, TADOCommand, TADODataSet and TADOQuery components with the equivalent UniDAC Components ?
My other area of concern is the SQL Syntax (which obviously is currently MS Access based and so uses none standard syntax such as IIF()). So I am interested in how the 'Unified SQL for writing server-independent queries' capability works and whether this would save us any time ?
Thanks in advance.
Stuart