Will
The cure I was given did work for a while but now the problem has
returned.
You do have a user "admin" as it is effectively the main operating system
tasks.
Strange, I can't find any trace of it (and Vista is quite good at managing
such detail).
I did some "googling around" and error 3260 in the context of MS Access
and
VB (which is how Legacy is built) is a problem regarding record locking in
the database. So, I think it is a bug somewhere and nothing we can cure
ourselves. I get the problem trying to do "set relationships" from one
machine where the database is on another.
I've solved it (for the moment). I noticed that one of the folders under
C:\Legacy was shared
and after a bit of searching I found it and switched it off. (How this got
there I don't know but must have been carried over when I transferred
settings from my XP machine to the new Vista laptop). So I can now use the
Potential Problems feature again (although I have noticed that the problem
reappears sometimes if I try to use an existing PP list).
I think you need to wait until the whole team is back from the cruise and
chase Support
Indeed. I didn't realise they were away on the cruise. I originally posted
the issue to them in early June when I was still using my XP machine and not
getting a response surprises me. Support has always been good in the past
but they seem to have been overwhelmed by the success of V7.
Cheers
Will
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
