[AccessD] New Database Table - How to Proceed

If your DBMS does not include a backup - restore and forward recovery facility
then:
Have the front end constrain all access to be via forms that means processes are
entirely controlled.
Have the front end post 'text' files (with date-timestamp as part of the file
name) containing the updates into a folder onto the server and  a backup
recording facility on a remote device.
Have a batch process take the data in those text files and apply it to the
database.
That process could also be the primary update facility triggered by a change
(new file) in the text file records folder 

JimB

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gary Kjos
Sent: Tuesday, March 25, 2014 1:37 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] New Database Table - How to Proceed

I think that people who haven't actually used Access often have a bias
against it. The "risk" of an Access DB would be possibly a corruption issue
that couldn't be recovered from excepting reverting to a previous backup.
With the amount of updates that would seem to not be a huge risk for your
application. Assuming that these updates could be reentered somehow and are
not being captured ONLY in the database without other documentation.

If I were in your place, I would be using an Access backend at least to
develop it. I would plan on having backups made at minimum every day with a
rotating cycle of daily/weekly/monthly backups so that if some catastrophic
issue was encountered you could go back generations if necessary as
sometimes there could be an undetected error with something that you don't
even realize there is a problem with.

Sql Server Express would be my upgrade plan or where the final version
would reside once the development in Access was complete or near to it.
During development you are likely to be fiddling with additional fields and
perhaps more tables etc. A single table?  Really?  Is that a well thought
out design?  And making those changes in the tool you are most familiar
with will speed your development.  On the other hand that would also be a
good opportunity to learn the procedures to do this in SQL Server too.

Is this a publicly held company?  If you are subject to audits using Access
for a business critical application might be looked at suspiciously where
SQL Server, even the Express version would be better accepted by outside
auditors.

Good luck!

GK


On Mon, Mar 24, 2014 at 4:15 PM, Brad Marks <BradM at blackforestltd.com>wrote:

> All,
>
> I have a question, but first I need to explain a little background.
>
>
-- 
Gary Kjos
garykjos at gmail.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com