1

Re: Linking R6 to Access

I originally asked this in another forum, but have had no solution offered. It is more appropriate here, so I am re-posting.

I noticed that the linked Access database I use for inspection was lacking a table.  Mike suggested using the tool at
http://www.jncc.gov.uk/page-5005 to create the new linked database, but that failed with the error 'System\DBPlugin.exe_ has stopped working'.

I have checked that R6 is in the default location, though the SQL database for some reason was installed in C:\Temp\Temp Recorder DB Location, and I have just left it there.

Trying to link manually through a new Access database fails as well, as the SQL database is not recognised when I try to identify the ODBC source.

I am using a standalone on Vista.

I would welcome advice on how to create a complete Access database linked to the R6 database.

Murdo

2

Re: Linking R6 to Access

Hi Murdo
I managed to get the tool running on Windows 7 64 bit though not without some fiddling, so these points should help on Vista.
1) First stop your SQL Server service, because the tool tries to start it and fails if it is already started.
2) Now start a command prompt by browsing on the start menu and right click to select Run as Administrator.
3) Use cd to navigate to the folder you unzipped the tool to.
4) Open up the bat file, copy its contents to the clipboard, then right click on the command prompt and paste this in and press return.

I chose to login using my windows account rather than sa (since my sa account is disabled) and it worked.

Hope that helps, I'll add an issue to the bug list about these points.

John van Breda
Biodiverse IT

3 (edited by MikeWeideli 06-01-2011 10:50:24)

Re: Linking R6 to Access

If  relinking to the Access database continue to fail, then you can create a new Access database and link it manually to Recorder 6.  The only problem with this is that the table names will end up prefixed with dbo_.  Depending on what you wish to do you can either leave it this way or change the names. You can change the name manully, or I can supply an access function will will remove the dbo_  automatically.

Mike Weideli

4

Re: Linking R6 to Access

This process should come with a very large warning sign on it. I have just attempted to run the tool and it had an entirely unexpected consequence which might have been disastrous (although hopefully I can put it right before anyone notices).

Since we originally installed R6 a good while ago, during which time there have been several updates to the database (including a number of tables I have added myself for various purposes), I've been wondering about rebuilding the Access Db to see if it would include any additional tables etc. I know I can add them myself, but I was curious (dead cats spring to mind here).

Safety first, I thought, so I renamed the existing Access Db to prevent it being overwritten, giving me a route to get back if anything went wrong.

So I downloaded the tool and ran it (having changed the default filepath as instructed). It failed to rebuild the databse (although it nicely informed me that the problem was minor and wouldn't affect the normal operation of Recorder).

However, when I looked in the Recorder/database folder, there was only one file, the new NBNData.mdb (an empty Access 97 database with no tables). My renamed copy of the original Access 97 Db had been erased, as had the converted Access 2003 version we use on a day-to-day basis (the 97 copy will only open as read-only on our system) and any other files which may have been in the folder (I don't yet know whether there were any).

Now I know I can rebuild the Database from scratch as described above, but that will not restore the numerous Access queries which we have added to the 2003 version to enable us to look at the data quickly in ways which would be much more difficult in Recorder itself.

I don't remember the last time I came across a program which erased the entire contents of a folder without warning or asking permission. I am flabbergasted!

Hopefully I will be able to restore the contents of the folder from our comprehensively backed-up system, so there should be no harm done, but this is really not good enough. The tool comes with a Read me file, but is there a warning in there? Nope.

There is of course a moral to this story, something about looking before you leap...

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

5

Re: Linking R6 to Access

Thanks, chaps.  And especially to Rob for warning of the glitch.  I think we would all expect a chance to abort before something that major was about to happen.  I will save it for a quiet moment after a lot of thought.  Maybe the easy option is to run with what I have, as I have all the linked tables I need for almost all purposes.

Mike - I have tried to link a new .mdb file to the R6 database, but don't seem able to see the latter to make the link.  I been through the dialogues and tried all kinds of things to no avail.

M.

6 (edited by MikeWeideli 06-01-2011 18:21:30)

Re: Linking R6 to Access

I have uploaded a Word Document which explains how to manually create the link.

http://forums.nbn.org.uk/uploads.php?file=Access%20to%20Recorder%206%20Link.zip

Mike Weideli

7

Re: Linking R6 to Access

Thanks, Mike.  That worked, though I had to find and paste in the server name at step 8, as there was nothing in the drop-down list.  It seems to be fine, though I have kept the old one just in case any problem emerges.  I have found the Linked Table Manager as well - in Access 2003 it is in Tools/Database utilities - so I will know where to go in future.

Thanks again for your efforts.

M.