BaseCamp needs an AutoSave function...

Former Member over 11 years ago

I am aware that others have asked for this function but they seem to be passed over or buried somewhere.

Please create an AutoSave function that can be turned on/off by the user. I'm not talking about the "Save Data upon Quit" function. I'm talking about a real AutoSave function that will save every change to the database as it happens.

The downside: a potential reduction in performance--waiting for the save but that should be done in the background.

The upside: significantly reduce the amount of user frustration when making time consuming changes to your database but BaseCamp crashes before you can do the "Quite/Save".

0 azdrmn over 10 years ago

BaseCamp does Autosave every 5 minutes. The performance hit to save on every change makes for a painful user experience, especially for large databases. I realize it is painful to lose any data though. We could look into a user initiated save.

0 Former Member over 10 years ago

I would give up performance to insure I didn't lose my work effort to a crash. Could you make that user initiated save a "Save on all Edits" preference? :cool:

0 Former Member over 10 years ago

The other main cool thing we can achieve here, is 2 machines using the same database. Basecamp is used within the Red Cross for search and rescue, and it would be amazing if 2 machines could work againt same DB (shared storage or Dropbox) at the same time. I know what people might think, but we need that :D

0 PSEABOLT over 10 years ago

I have been using dropbox for several years to sync and share one database on 3 macs. There are instructions on the form how to enter a terminal command but I think with the BC preference command (choose Library) all you have to do to have the same dropbox account on both computers, move the BaseCamp folder to dropbox and use the advance preferences in BC to choose the folder.

0 Former Member over 10 years ago

SUSAMB, you can probably close this topic as I think we have exhausted the "Autosave" discussion and we have now digressed into the "sharing databases topic"--again.