Importing from another genealogy program? This is the place to ask. Questions about Exporting should go in the
Exporting sub-forum of the General Usage forum.
-
colinjenke
- Newbie
- Posts: 4
- Joined: 10 Feb 2016 01:09
- Family Historian: V7
Post
by colinjenke » 28 Apr 2023 18:29
Mark1834 wrote: ↑28 Apr 2023 07:30
A belated welcome to FHUG, Colin.
Could you clarify exactly which plugin you have used please, and what you are trying to do? The plugin in the above post relates to an older process that is now obsolete.
The supported method for linking FH with an Ancestry tree extract in a way that supports hint continuity is to use the
Ancestry Synchronization plugin from the Plugin Store. This utilises developments in FH that enable a far more reliable method for linking records in different apps and updating RM/Ancestry data, but is limited to more recent versions of FH7.
Incidentally, there is a major update to the store plugin currently being finalised, and will be published in mid-May once user testing is complete.
Thanks Mark, I am using V7 of HM and the plugin i am using is Ancestry Synchronization v1,
Item 1 Plugin compare ok
Item 2 Plugin export ok
Item 4 Plugin update is the one i am having the error (appears to happen when it gets to places)
REGARDS
-
Mark1834
- Megastar
- Posts: 2145
- Joined: 27 Oct 2017 19:33
- Family Historian: V7
- Location: South Cheshire, UK
Post
by Mark1834 » 30 Apr 2023 09:04
Colin,
I've looked at the error message in more detail, and it clearly arises from a malformed SQL statement used to either update or delete a record in RM (which is why you are only seeing it when updating). However, all it tells me is that the error occurred in the SQL library, not exactly where and when in the plugin.
Some extra background would help please. Has the plugin worked correctly in the past? If so, it is probably caused by a recent change to your project. Is it an unexpected difference between RM7 and RM8/9?
I sent you a direct message with my e-mail address on Friday. Hopefully, I'll be able to identify the problem if you can send me a copy of the GEDCOM file produced by the plugin (and the RM file) please. If not, I'll send you a diagnostic version of the plugin that will generate additional output that will help to locate where the problem is.
Mark Draper
-
colinjenke
- Newbie
- Posts: 4
- Joined: 10 Feb 2016 01:09
- Family Historian: V7
Post
by colinjenke » 30 Apr 2023 19:06
Mark1834 wrote: ↑30 Apr 2023 09:04
Colin,
I've looked at the error message in more detail, and it clearly arises from a malformed SQL statement used to either update or delete a record in RM (which is why you are only seeing it when updating). However, all it tells me is that the error occurred in the SQL library, not exactly where and when in the plugin.
Some extra background would help please. Has the plugin worked correctly in the past? If so, it is probably caused by a recent change to your project. Is it an unexpected difference between RM7 and RM8/9?
I sent you a direct message with my e-mail address on Friday. Hopefully, I'll be able to identify the problem if you can send me a copy of the GEDCOM file produced by the plugin (and the RM file) please. If not, I'll send you a diagnostic version of the plugin that will generate additional output that will help to locate where the problem is.
Thanks Mark, I have not been able to find the email that you sent me, Have checked my profile and my email address is correct in the profile. Could you please resend, thanks.
-
Mark1834
- Megastar
- Posts: 2145
- Joined: 27 Oct 2017 19:33
- Family Historian: V7
- Location: South Cheshire, UK
Post
by Mark1834 » 30 Apr 2023 19:48
Done - should be shown as from Family Historian User Group (FHUG), subject Ancestry Plugin.
Try your Junk Mail folder if it hasn't got through directly!
Mark
Mark Draper
-
Mark1834
- Megastar
- Posts: 2145
- Joined: 27 Oct 2017 19:33
- Family Historian: V7
- Location: South Cheshire, UK
Post
by Mark1834 » 01 May 2023 21:07
Colin kindly shared his export file with me, and the problem arises with date phrases containing quotation characters, as these are not escaped when creating the SQL statement that updates RM.
I’ve shared a temporary fix with Colin, and a more permanent one will be incorporated into version 2 of the plugin later this month.
Mark Draper