I have a dropbox folder on my local drive which is where the legacy fdb and pic files reside. This is the same approachk as used by many other users without problem and s working great except for this glich with the geo source file. I can[t say for sure that the problem started when I changed to this setup but suspect it did. Tom
On Sat, Jul 13, 2013 at 7:20 AM, Paul Gray <[email protected]> wrote: > Mike, > > I must disagree with your comment about using Dropbox as only a backup > mechanism. Putting your 'active' Legacy file in there was never a problem > for me. With Dropbox, you have a local folder resident on your PC in > addition to the one in the cloud, and when using Legacy you are using the > local copy. It works just fine. > > What Legacy, and many other programs, can't handle is when the one and > only copy of the file is on some cloud server. But that isn't how Dropbox > works. > > Paul Gray > > > > -----Original Message----- > From: Mike Fry [mailto:[email protected]] > Sent: July-13-13 1:43 AM > To: [email protected] > Subject: Re: [LegacyUG] Error code 76 when going to geo databas > > On 2013/07/13 03:58, Thomas Ramey wrote: > > > I recently moved my data file and pics to dropbox. It is installed > > c:\dropbox\legacy and utilizes the same folder names as in the > > original c:\legacy. All seemed to work well until I went to go to a > > geo lookup. I get a runtime error 76 and then get kicked out of the > > program. Help file says to reset the temp file on the locations > > folder which I did even though it was correct as c:\legacy\temp. No > > solution. I uninstalled my geo codes and reset them back up. No > > help. They are in the c:\legacy\geo. No help. I tried changing the > > temp file to the dropbox folder. no help. I would appreciate any > > ideas. Running current build on Win I. Tom > > Are you trying to use Dropbox as a working environment? Then you're going > to have serious problems. Dropbox should only be considered as a backup > mechanism. > > -- > Regards, > Mike Fry > Johannesburg (g) > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
