Jump to content


Photo

Declare DLL call caused an exception. 21 GRINDNAMES


  • Please log in to reply
7 replies to this topic

#1 easouza

easouza
  • Members
  • 7 posts

Posted 18 November 2013 - 05:38 AM

I am unable to import FTM 2008/2009 files produced by FTM 2012 and FTM 2014 into TMG8.  I have no problem importing these files into TMG7.  I am using Windows 7 Pro 64-bit.  Every time I try to import I receive the error "Declare DLL call caused an exception.  21 GRINDNAMES."  I completely uninstalled TMG8 and reinstalled it using the latest version that I downloaded today from the web site.  I still receive this error.  What else can I do to alleviate this problem?

 

 



#2 Jim Byram

Jim Byram
  • Moderators
  • 7,340 posts
  • Gender:Male
  • Location:Framingham, MA

Posted 18 November 2013 - 07:04 AM

I tried a FTM 2009 import and got no error messagebox but no sources were imported so something has been broken. There was an internal "gbSource DLL syntax error" every time a source import was tried.

 

Let me see if I can get this resolved and if I can do that, then I'll come back and ask for your project to test.



#3 DavidW

DavidW
  • Members
  • 2 posts

Posted 05 December 2013 - 05:14 AM

I was trying to import a Legacy file directly into TMG (UK 8.08) and it gave a gbSource() DLL Alias name already in use - error message. The file imported but without any sources.

Importing via GEDCOM, the sources were present. (Win 7, 64 bit). So it's not just a FTM import problem.



#4 Jim Byram

Jim Byram
  • Moderators
  • 7,340 posts
  • Gender:Male
  • Location:Framingham, MA

Posted 05 December 2013 - 06:14 AM

I've added David's information above to the bug report. The GenBridge files were last updated 22 Jun 2011. That seems to be a long time to go without anyone finding this so the problem might have to do with the gbimport.app (that is used for both FTM and Legacy import).



#5 DavidW

DavidW
  • Members
  • 2 posts

Posted 10 December 2013 - 04:58 AM

Jim, I found a couple of older installation files and have tried importing a Legacy .fdb file to these older versions.

In v8.00 it works ok and the sources are imported, but in v8.06 it is broken (I didn't have anything inbetween) as it still is with v8.08.

I hope that helps to localise it a little...



#6 Jim Byram

Jim Byram
  • Moderators
  • 7,340 posts
  • Gender:Male
  • Location:Framingham, MA

Posted 10 December 2013 - 08:54 AM

David...

 

The GenBridge DLLs have not changed since TMG 8.00 so this is not a GenBridge issue and should be possible to fix.

 

Jim



#7 rwithrow

rwithrow
  • Members
  • 2 posts

Posted 29 January 2014 - 02:11 PM

Jim,

 

Has this problem been addressed yet?  Any idea on how soon a fix will be ready?

Robin



#8 Jim Byram

Jim Byram
  • Moderators
  • 7,340 posts
  • Gender:Male
  • Location:Framingham, MA

Posted 29 January 2014 - 02:57 PM

I just posted this in another topic. The gbimport issue affecting FTM and Legacy was automagically fixed between two beta builds sometime in the second half of last year. Hopefully, these imports will work in the next release version. Note that Legacy8 import is not supported and some of the later Legacy 7/7.5 builds might have issues since there were a number of Legacy structural changes after the GenBridge import was last worked on. GenBridge hasn't been updated since mid-2011.

 

The last TMG version where the FTM and Legacy imports worked was v8.04. Whatever broke the imports in v8.05 didn't involve either GenBridge or the import apps.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users