[AccessD] Automatic backup

Stuart McLachlan stuart at lexacorp.com.pg
Thu Mar 17 15:50:14 CDT 2016


Me too!  Split it!



On 17 Mar 2016 at 10:18, Jim Dettman wrote:

> 
>  Can't second what Lambert said enough...there's no real downside
>  (well just
> one and it's minor).
> 
> <<I can't imagine a time when more than one person will be updating
> records - we're going to have an employee (not me) dedicated to
> that.>>
> 
>  Never say never...
> 
> <<I want to add a backup routine that runs when anyone closes the
> database.>>
> 
>  You can't do that inside in any easy way from inside your app while
>  it's
> executing.   To keep things simple, just setup a batch file with a
> shortcut on the desktop.  The batch file doesn't have to be anything
> more than a file copy and you'll probably want to suffix the date/time
> on that.  Let me know if you want an example.
> 
>  Your other option would be to write it in VBA in a small utility DB,
>  again
> assuming you want to keep it simple.
> 
> Jim.
> 
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> Of Heenan, Lambert Sent: Thursday, March 17, 2016 10:03 AM To: 'Access
> Developers discussion and problem solving' Subject: Re: [AccessD]
> Automatic backup
> 
> There is ALWAYS a reason to split. Do not hesitate , do it now. It
> will take you five minutes and save you lots of potential trouble down
> the road.
> 
> For one thing it helps protect the data from corruption. It makes it
> much simpler to do development work on the front end. And one day
> there might be two people needing to access it simultaneously. Much
> better for users to have their own copy of the front end.
> 
> Lambert
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> Of FW Salato Center Sent: Thursday, March 17, 2016 9:41 AM To: Access
> Developers discussion and problem solving Subject: [AccessD] Automatic
> backup
> 
> I want to add a backup routine that runs when anyone closes the
> database. There aren't any action queries or anything like that at
> this point and although it will be on a server, I can't imagine a time
> when more than one person will be updating records - we're going to
> have an employee (not me) dedicated to that.
> 
> Currently, there's no reason to split it, so I'm not going to. So, a
> backup routine should be fairly simple. I can train the other employee
> to do it manually and she will - she's competent and even if she
> forgot occasionally, updates are very limited. Most of the info is in
> there and they want reports - updates are ... there are updates, just
> not daily and not a lot.
> 
> I'm thinking... train her not worry about it. We have electronic and
> paper files of all the updates and reentering would take... at the
> very worst a few hours if the worst happened.
> 
> Recommendations? Thoughts?
> 
> Susan H.
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 




More information about the AccessD mailing list