Access database on 2 computers

My service company is expanding and I going to need to hire someone to assist me in the office. My concern is I run the company from an access database that controls all customer contact info, invoicing, and memos.

With now two computers working, how can I get all the info back to one database. Ie: if my assistant makes changes to an invoice or adds an invoice, how can I get that to one central database?

You have a couple of choices. If you have MS SQL Server I would upsize your database to this.

Otherwise, you can move the tables in to a new backend database which is linked to the front end which has your queries, forms etc. Each PC that needs it can then have a copy of the front end and all the data is therefore shared as it is stored in the backend database.

Then it is not quite clear what your question is here...
(Because splitting the db is what both JEaston and myself are suggesting)

A Split database is the standard way of allowing multiple users update the same data.
(which is what you seem to be asking about here)

So, sure you can run an unsplit database if the concurrency is always going to be low, and/or the likelihood of two users updating the exact same field/record will also be rare.
(Only two users)
But what happens when this increases?
What happens when your app matures and you have automation that may result in edit conflicts if the db is not split?

Even if you upsize the Backend to SQL Server, you still need a front end in each users workstation.

In other words, if you are sure splitting the db is not the solution, then what other technology are you looking for?

<it has been years since I have split an access database! >
In the same way that someone can claim that it's been years since they backed up their data (and they have never had a HD crash).
Or that it has been years since they have updated there Antivirus software, and never gotten a virus/Trojan/malware

So again, (unless we are misunderstanding your question), I am not sure what you are looking for here...

Another approach is to change it to a web application.
It requires extra knowledge to develope, but has the following advantages:
One application on server,
Browser as fron end.
Ease of adding other users.
Can be accessed remotely.

@boag2000: I think you read my second comment and thought it was from the author. I was just replying to you, although on re-reading it I missed the word 'server' in the line "if there is not a database server to upsize to"

If your haven't used MS SQL server before then you may find this more restrictive. It is more powerful, but changes how you manage tables etc as it can no longer be done from within access. In terms of cost I believe there is a free verision with some size limitations. It is worth learning if you ever plan to develop applications with more than a handful of users.

The difference between upsizing (to an SQL Server) or splitting (into front end and backend access files) is not huge. It is a different process, but the principle is the same - move the table to the new backend and then link the front end to the backend.

Technically speaking I would say SQL is by far the better. It has better backup solutions etc, but you do need to learn a whole new application.

If your looking for a simple solution and don't expect there to be more than a few users I would go with splitting the database. You can alway move a split database to SQL Server in the future.

Folks .. let's keep this simple. The OP has 2 users and 2 computers.
The most logical, practical solution - is .. ad already suggest to 'split' the db into a Front End (everything but tables) and a Back End (tables only). I'm sure the links provided by Boag2012 are sufficient for showing how this is done.

Put the BE on one of the computers (I suggest the OP's computer) - and a copy of the FE on both computers, linked to the BE. Done.

SQL Server and web are total overkill for this in terms of complexity and learning curve.

@DatabaseMX: I agree in general terms if users will stay small. If it is expected to grow then thinking about progression to a server solution never hurts. Developing a web application is a huge step - I have several web based systems which started life in Access.

"stay small."
Well ... I won't debate SQL Server - and of course, you really can't go wrong with SQL Server. But, based on the description of the OP's situation - I'm thinking Access - especially since the OP already has a function Access db.

I agree with MX - discussion of moving to SQL Server or rewriting of a web app is very premature for the scenario that the OP described. Merely splitting the Access database and running the FE on two different PCs, as MX described, should be completely sufficient.

It's some code that you simply copy into your front-end application. It handles multiple Access back-end databases, ignores non-Access tables, and can automatically and silently relink to back-end databases in the same folder as the application (handy for work databases or single-user scenarios). There's a ReadMe table with instructions.

Featured Post

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.