Newbe question

[justhininabouti]

I have been considering an Access employee DB for my company for a while now. I have started to build a few tables, and like the direction this is taking me. One major concern I have will be data integrety/availability.



The environment this DB will be used in is this...

My company is operates 3 ships. we have a number of employees that can work on any one of the ships. Each ship will need to be able to update any of the DB data for the employees that are assigned to it. They will also need to be able to access (view) data on any of the other employees. The office should also have access (edit) to all employees at any time.

We do not have an 'always on' internet connection on the ships. however the office does, and operates a server for their website. The ships use dial up internet access (Cellular wireless card), and have a connection about 60% of the time.

My question is this what (If any) method should I investigate to allow the type of access discribed, while maintaining data integrety? I have seen referance to a front-end/back-end setup, but I am a little fuzzy on how this relationship works, or if it would be approiate for my purpose.

Any advice would be appreciated.

[June7]

Split db means the data tables are in a file that resides on a central server (the backend). This file can be Access, Oracle, SQL. The frontend has links to the backend tables and also the queries, forms, reports, and code that serve as user interface to the data. Each user runs their own copy of the frontend. This works best on a local network. Internet connectivity is another issue. Some use Sharepoint for that.

[justhininabouti]

June7 -

thanks for the reply.

That's kind of what I thought about the FE/BE solution.

It looks like sharepoint could be the answer to the data integrety problem. That gives me reason to move forward. It will add to the complexity of the project, but I have nothing but time. I'm one of the guys that work on the boats. with all the downtime I have I should have time to work out the details.

I would still be interested in other possible solutions.

[June7]

I have no experience with Sharepoint or any other web database. Good luck.

[justhininabouti]

Thanks for the well wishes. It will be a challange. Trying to learn Access, studying DB design so I can make something functional, and now looking forward to learning Sharepoint (If that turns out to be the best solution). But, like I said I have time. I just don't want to spend a bunch of time creating a DB to find that it will become corrupt in a few days because of our environment.

I still welcome any advice.

[June7]

Review this recent thread about another posters experience with Sharepoint and their solution https://www.accessforums.net/access/...ase-18672.html