Best Practices question

  • Thread starter Thread starter RickB
  • Start date Start date
R

RickB

Good day,

I have a membership database which must be accessed by 3 or 4 people.
However, these users are not on a shared network. Data entry is done by one
person. The other users only need to view the data and occasionally create a
query or two.

I created a process in VBA for the primary user which makes a copy of the
tables in Excel format, combines the spreadsheets into a ZIP file, and then
sends the zip file to the other database users via email. In turn, the other
database users then utilize another process I created which then makes a
backup of there existing tables then imports the spreadsheets from the
emailed zip file into the database overwriting all existing data.

Short of creating a new application that is accessed via the web that
everyone could access, is this solution acceptable and if not, what would be
the best solution for this small group to share a database?

-rick
 
Not sure if you would be better just sending out the database and cut out
the phaaaphin' around with Excel.

This assumes that you have already split the database into a front end
(everything except tables) and a back end (tables only), and that is best
practice.

The users can create their queries on their front ends and the back end can
be sent out to replace the existing back end.
 
Back
Top