Caught out by the Reply To trap - this was intended to go to the list... ---------- Forwarded message ---------- From: Tom Holden <ve3meo@gmail.com> Date: Wed, Sep 24, 2014 at 11:01 PM Subject: Re: [TMG-REFUGEES] RM SQLite renumber RIN/TMG_ID To: Sheila Altenbernd <sheilaxyz1@gmail.com> RootsMagic operates on one database (Project) at a time, does not have the concept of what TMG calls data sets within a database, but does support multiple databases being open at the same time with the ability to drag'n'drop persons between databases. So persons with TMG_ID facts transferred to another database will get new RINs and then one could run the script to re-match their RINs to their TMG_ID fact, provided there are no conflicting, pre-existing RINs. As I mentioned in my reply to Lorna, the script was designed for immediate post-import use and would need revision or even incorporation into a higher level app to protect against exceptional uses. Of course, backing up before or running the script against a copy of the database is always advisable. Thanks for your appreciation, Sheila. I was a Family Origins user for a while and then had a hiatus of some years; when I got back into it, FO was deceased, RootsMagic 3 was current and RM4 was in the offing. I looked around at others (I think even TMG) and was drawn to FO's grandchild, despite its disrupting shift in database technology because of two things: a) the open-source, free database and b) the active and supportive on-line user community. You will have little challenge in SQL syntax for SQLite and we have done our best to document what we believe the database design to be - the biggest challenge is time but you should find many of the published queries may suit your needs or can be readily adapted. Tom On Wed, Sep 24, 2014 at 10:06 PM, <sheilaxyz1@gmail.com> wrote: > FYI -- TMG has an edit that won't allow the entry of a duplicate TMG_ID. > She must be maintaining two different projects. Since they are separate > there is no duplicate ID issue. She wants to link the two projects after > the fact, so if Person XYZ is TMG_ID 5 in the first project she forces the > TMG_ID to be 5 in the 2nd project. This simplifies linking them when she > builds her web sites. (At least that is what I am understanding her to > say). > > I'm understanding you to say the RootsMagic will also support multiple > projects. She could force the IDs to match by updating the TMG_ID Fact and > rerunning the utility. The major difference being that TMG would not allow > a duplicate TMG_ID to be introduced, but RootsMagic could result in a > duplicate TMG_ID Fact. Running the utility with a duplicate TMG_ID Fact > would result in a corrupted database. She can continue doing as she has > been, but will need to use some extra care. > > Thanks for your ongoing support and willingness to answer questions. > RootsMagic is missing some functionality that will cause me headaches > (alternate name variables and memo variables in sentences), but it does > appear that RootsMagic has the best chance of eventually meeting my needs. > The SQLlite database is a big plus. I've never used SQLLite, but as a SQL > Server database administrator I'm sure I can easily pick it up. Obviously, > a lot of care needs to be taken when running scripts against the database, > but at least there is the possibility of simplifying the necessary clean > up. The other advantage is the support. The Legacy RootsWeb mailing list > has had one message posted this month. And, you see no one on this list or > the main TMG list posting about the benefits of Legacy. > > I went ahead a purchased RootsMagic a few days ago to begin testing the > direct import and playing with it. I should have waited a couple of days > so I could save $10!!! > > Sheila Altenbernd > >