Hi Estelle
Cathy is correct that the backup file is the normal zipped
version.
I would guess that the issue with numbers added to the end of
the file name is because you are saving it to one of the cloud based systems,
like OneDrive or Google Drive.
Certainly, it is a known problem with Google Drive adding (1) to a file name
when it is saved to the Google Drive folder before Google Drive had managed to
sync the files back to the cloud version. Since Legacy technically does not
write a new file, I would assume that when it closes the .fdb file it is
treated as being a new file version.
I have just tried that out on Google Drive and it does not seem to have a
problem, but it might be different on how your system is setup, where you are
saving files, whether you are using a cloud solution and on the connectivity.
Regards
Chris
From: LegacyUserGroup [mailto:[email protected]] On
Behalf Of Cathy Pinner
Sent: 21 December 2017 22:24
To: Legacy User Group <[email protected]>
Subject: Re: [LegacyUG] File name problem
Estelle,
You should be making backups every time you leave Legacy. That does not add [1]
to the filename. The backup automatically has a unique name as it adds date and
time to the filename - if you don't interfere.
That is not the source of the problem you were having.
I think it was what you were doing when opening Legacy I think - using the
backup in the wrong way.
I hope you have it sorted and you're not using a file that is in a temp folder
on your computer.
Cathy
E. Nad wrote:
Hello everybody,
Thank you all for the help and relevant solutions.
It now works as it should.
The source of the problem was my making backups everytime I left
Legacy. As I was keeping the same file name on and on, Legacy added a
[1] to the file name every time.
Thanks again for the help, I am so impressed with the efficiency and
readiness to help of users from all over.
Yours truly,
Estelle Nadeau
[email protected] <mailto:[email protected]>
------------------------------------------------------------------------
*De :* LegacyUserGroup <[email protected]
<mailto:[email protected]> > de la
part de Chris Hill <[email protected]
<mailto:[email protected]> >
*Envoyé :* 18 décembre 2017 11:22
*À :* 'Legacy User Group'
*Objet :* Re: [LegacyUG] File name problem
Hi Estelle
There is a very ‘hidden’ option within Legacy to prompt to save on
exiting. This is from the *Help* on *Exit Program*.
*/Automatically Prompt for Backup /*
*//*
/With this box checked, Legacy offers to make a backup file for each
Family File that was opened during the session. (See Backing Up a
Family File for more information on making backups.) /
/ /
/These options can be set from the Customize screen reached by
choosing Customize from the Options tab on the Ribbon bar and then
choosing the Other option on the menu panel. Click the Turn on
Optional Reminder Messages button. From the Optional Reminder Messages
screen, click on the Reminder to make a backup when exiting Legacy
option./
To change these settings, you need to open the *Customise* dialog from
*Options* – it is the left entry in the Options ribbon bar. You then
select *Option 12 – Other Settings* and then click on the button below
*12.5 Message boxes*. This will open a dialog with a number of options
that you can configure. You have probably got the third one under
*Prompts/Reminders* (left tab) set, which is *Reminder to make a
backup when exiting Legacy*. Clear that option to stop Legacy asking
for you to make a copy of your database.
In practice, you DO NOT NEED to ma ke a copy of your database, since as
a fully managed database it is always kept up to date. I suspect that
every time you run Legacy you are then opening the latest copy and
then saving it again, thus adding the [1] onto the file name. Hence
you should be finding that you have a set of files in your PC reading
A.fdb, A [1].fdb, A [1] [1].fdb … etc. In this case, you need to open
the latest version and then use the *File* and *Save File As* option
to create a new file with a clean name.
You only need a single .fdb file as your working database. If you need
a backup, then use the *File* and *Backup File* to create a compressed
copy of your database, and remember not to copy it to the Legacy Cloud
unless you want to. I would make backups before making major updates,
check/repair or merges from other trees.
Hope this helps.
Regards
Chris
From: LegacyUserGroup [mailto:legacyusergr [email protected]
<mailto:[email protected]> ]
On Behalf Of E. Nad
Sent: 18 December 2017 15:08
To: [email protected] <mailto:[email protected]>
Subject: [LegacyUG] File name problem
(...)
--
LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/
