1

Topic: version 6.18.1.259 question

Having upgraded from version 6.17.1 to 6.18.1 (release candidate) a few weeks ago and finding that a bug prevented me from doing an R3 import via bulk move and that Mike's subsequent suggested work-around did not resolve the problem, I uninstalled R6 this morning and re-installed version 6.15.4 from disk. I then installed the required R3 import addin, but once again I received an unhandled error message when I attempted to run the import.

I notice that my Help: 'About Recorder 6' details show my version to be 6.18.1.259, not the 6.15.4 that I expected.  How did this happen? So, if it is the case that I'm still lumbered with the release candidate 6.18.1, does that mean that when the approved updated version is released I just need to install it in the usual way and not have to upgrade from 6.15.4 to 6.17.1 first?  I realise that I shall have to do all the dictionary upgrades.

Finally, is there any news about when the new 6.18.1 is likely to be released?

2

Re: version 6.18.1.259 question

I can't think why the unistall  didn't remove everthing.  After the install  of 6.15 did you end up with a blank database, or did you select the option to retain the database when you did the 6.15 install ?   If your database still contains the Organism table then it wasn't replaced.  We are testing the 6.18.1.260 today specifically to see if the Recorder 3.3 transfer will now work. If it does then we will release it Thurdsay.  I am not sure now what the state of your system is. It sounds like you still have the  the 6.18.1.259 database  attached (ie with a poulated Organism Table)  to your version of R6. In this case you will just need to run the new new release (build 260) when it is available.  If not then you will need to run the new build and update the Dictionary. You only need the one upgrade from 6.15 to 6.18 and do not have to upgrade to 6.17 first. If you need to install a new  copy of R6 with a blank database then you can obtain version 6.17 from www.Recorder6.info/Standalone.zip

Mike Weideli

3

Re: version 6.18.1.259 question

Thanks, Mike, for the helpful information. Where should I look to find the Organism table, please? In reply to your question about whether or not I accepted the option to keep the existing database. I can't remember.  I tried a moment ago to explain in detail what I did, but tied myself in knots and deleted it.  The thing is that initially i didn't uninstall the existing 6.18.1, but, wishing to keep it for later use, I renamed it in the same folder (Program Files) with a couple of 'z's in front.  I installed 6.15.4 as a temporary measure simply to generate, with DMAP and AditLink, a load of maps that I need.  When I found that the newly installed R6 didn't do it either, I uninstalled it, and then removed the 'z's from the original 6.18.1. For some reason that I forget, I tried to uninstall it, with the intention of having another go at installing 6.15.4, but couldn't locate it in the add/remove programs list.  I think I re-installed 6.15.4 anyway.  I wish I'd never started.  I look forward to Thursday.
Where is the Organism table, please?

4

Re: version 6.18.1.259 question

I must admit I am not sure where you are. I suspect Recorder has continued to point to the same instance of SQL Server which is why you are seeing  the 6.18 database. Renaming the folder probably did nothing to change things.  If the report Wizard offers you the option to Report on Kingdom/Class/Order/Family etc. then you definitely  still have the 6.18 database installed. I am hopeful that 6.18 Build 260 will sort it all out, if not we will have to work out what the situation is and get you back on track. If we can't release the build on Thursday then I suggest you backup the current database (6.18) and secure that and then  load version 6.17 to do the work you require. If it comes to this I will give you further help. Do you have the SQL Server Management Tools installed ?    They would make things easier, but are not essential.

Mike Weideli

5

Re: version 6.18.1.259 question

I have just completed a test of importing Recorder 3 data into an empty copy of R6 v6.18.1.260 and it worked as expected. Provided I don’t find any problems with the other tests I have planned we should be able to release v6.18 very soon. If you use Management Studio to access the Recorder 6 database you will see the Organism table in amongst all the other R6 tables but if you use the linked Access database (nbndata.mdb) you won’t see it unless you link it in using External Data – More – ODBC Database – Link ... – Machine data Source – choose a data source or create a new one – dbo.ORGANISM. This brings it in with a table name of dbo.ORGANISM so it appears amongst the Ds not the Os, however you can just rename it ORGANISM.

Sally Rankin, JNCC Recorder Approved Expert
E-mail: s.rankin@btinternet.com
Telephone: 01491 578633
Mobile: 07941 207687

6

Re: version 6.18.1.259 question

I cannot find an option with the report wizard to report on kingdom/class/order etc.  I've already tried that other option you suggested without success.  I'll see what transpires when the 6.18.1.260 is released and if I cannot get the thing to import my data from R3 then I'm calling it a day with R6.  Many many thanks for all your help in the past.

7

Re: version 6.18.1.259 question

Bob

I am sorry you feel that way. The Release candidate was what it said, a trial release for those willing to take a bit of a risk, before we released it fully.   We are very willing to give you the support necessary to get your import done and Recorder back up and running as you require so I hope you will reconsider and allow us to do this.

Mike Weideli

8

Re: version 6.18.1.259 question

Yes, of course.  Thanks again.

9

Re: version 6.18.1.259 question

Mike, I have installed the files you sent me this afternoon and they've solved the problem.  i have imported the R3 export files successfully and generated the 200+ distribution maps that I wanted.  Thank you very much for your help.