1

Re: Data Transfer from Recorder 2002 to Recorder 6.13

Hi
I think I've got 6.13 installed using MSDE, SQL Server 2005 Express & SQL Server 2005. The data transfer utility functions on the first two, but not the last. Recorder appears to function OK and will import data, but on trying to transfer data, it runs through all its routines, counts all the records in the tables but transfers none.  No error messages are displayed or seem to be written.
Can anybody help please?
Dave

2

Re: Data Transfer from Recorder 2002 to Recorder 6.13

Hi Dave,

When performing a migration from Recorder 2002, the database migration tool must be run on the SQL Server itself. Otherwise SQL Server cannot see the Access database files you are migrating from, which must be somewhere on the C drive. This is normally not a problem for MSDE and SQLExpress which are installed on your machine. However, with SQL Server (full version) you are likely to have it installed on a machine on the network somewhere, hence the problem. What you need to do is copy your Access mdb files from your Recorder 2002 install database folder to a temporary folder on the C drive of the SQL Server machine, then run the migration executable actually on that machine. You don't need Recorder installed on there - the migration will ask you where the mdb files are.

Simon

Simon Wood
[url=http://www.dorsetsoftware.com/]Dorset Software Services[/url]

3

Re: Data Transfer from Recorder 2002 to Recorder 6.13

Simon
Thanks for the reply. I knew everything had to be on the same drive and I thought it all was. I'll go back and double check. It might all be on drive E: on the server, would that be a problem?
Dave

4

Re: Data Transfer from Recorder 2002 to Recorder 6.13

Recently this issue has raised it's head again. 

When migrating data from 2002 to Recorder 6 on SQL 2005 (SQL Express or full versions),  the process may appear to run successfully, however not actually transfer any records to the SQL database.  This has been found to be an permissions issue with regards to the account the SQL Server service is using.

The account that the SQL service is using can be found and modified under:
Start Menu -> Microsoft SQL Server 2005 -> Configuration Tools -> SQL Server Configuration Manager
From here open up the properties of the relevant SQL 2005 Instance service.  The 'Log On' tab will identify which account the service is running under.   If it is set to 'Network Service' in the built-in account drop down, then the migration will probably not work.  This is due to the restricted permissions of the Network Service account. Change this to the 'Local System' account and apply the changes (this will prompt for a restart of the SQL service).  The Local System account has a greater set of permissions which will allows the Recorder migration process to work successfully.

For network installs the SQL service account may be set to a domain account.  If this is the case, the account needs to have permissions to write files to the same directory as where the SQL data files are situated (best to discuss with your systems administrator).

Simon Wood
[url=http://www.dorsetsoftware.com/]Dorset Software Services[/url]