Well I guess I must apologize to the list! I seem to be the one who started all this 3022 3021 error thing about a week or so ago, but from the direct e-mail I got it must have been a lot worse than most realized! What set me off was just as most have said I got canned messages back with no help at all. In my exchanges with Jim terry ? I believe it was he dropped a couple of names in the text I waited till they showed up and ask them for help. I got help from Michel Let me tell you I got help in every way he could help me! He found the problem.. He told me what to do and I installed this JET Update dated Oct 2000 instantly in two or three of my computers, tried various files and it seemed to be clear!!! Needless to say I have installed it in all my computers that I have as I could create this error in every one of them! It seems to have cleared the problem! Now my problem is to get my file of over 100,000 in some order!! I think I can! I HOPE I can I also sent a file to Legacy that has children in it that has no parents?? Got No answer Yet! But it was late last week. I am wondering what has happened to these parents?? Again I will apologize to the list but it seems we at least got something fixed for some of us! Now lets move on to other problems ! Thanks again to Michel! Gene -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michel Lacoursiere Sent: Monday, September 10, 2001 10:45 AM To: [EMAIL PROTECTED] Subject: Re: [LegacyUG] 3022 errors and JET update > As far as Jet 4.0 Service Pack 5 goes, unless you are having some unusually > persistent problems I would not bother with it UNUSUALLY persistent problems. There are a numbers of users that have been complaining for MONTHS that they can not add or import individuals in there file because of an error 3022. Updating their file isn't any good. Exporting to a new file is just a temporary work- around. You can delete all the user files you want that won't fix the problem either. There are users out there that never experienced that error but could at anytime if they don't install that SP. The Legacy test list was told on November 07, 2000 to install that SP. Those who didn't, started to report this error 3022 . On December 27, 2000 they were reminded that if they didn't install that SP they should do so. They all then reported that installing that SP took care of their problem. NO ONE on that list been able to reproduce this problem since then. The only tester that has been able to reproduce it wasn't there at that time. He just installed the SP and he is now reporting that it took care of the problem. Your "canned" reply regarding this error 3022 should have been update THEN. It would have save a lot of users a lot of headaches and file corruptions that have been reported. Michel Lacoursi�re [EMAIL PROTECTED] To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp
