Simple Shared Database ?

[chapelman]

I'm looking for a database to use on two PC's in different locations, which can be either manually or automatically synchronised. I'm not teriffically techy so it has to be fairly simple to operate. It doesn't need to be terribly complicated as it's just to keep track of clients and the services we have provided them with, maybe about 20 user definable fields.

Where I am struggling to find anything is with the synchronisation. We've tried Act but that really seems too complicated for what we want, and the synchronisation feature just wouldn't work in spite of spending hours on Act forums, looking through the manual. Access might be a possibility as I've used it on a single PC before, but I'm not sure about the synchronisation thing. It would be useful if the database fields could link in to a mail merge on Microsoft Word, but if it could export fields to an Excel spreadsheet then that would do instead.

I suppose I'm looking for a kind of muppets version of Act without all the features, something that could be picked up in an hour or so.

Any ideas would be greatly appreciated?

[chapelman]

Just a quick thought. On reading my posting it seems that a simple client management program rather than full database might be the answer. So with regard to the criteria in my first posting, again

All suggestions greatfully received?

[ozbon]

No idea offhand.

You could create something using OpenOffice's database. Alternatively, if those two PCs will always be online, you could do it through a web-based front-end, and run the entire thing like a website.

I've done the latter option more times than I can count, so feel free to drop me a PM with your requirements, and I'll give you a quick quote.

[DotNetWebs]

If you are just using a file based database like access, and are happy to manually sync as required, the something simply like this might do:

https://www.foldershare.com/

Regards

Dotty

[FireFleur]

Could use SQLite, it has an ATTACH command that allows multiple databases to be attached, and then merged using SQL commands.

A good book (well the only book at the mo) on SQLite is The Definitive Guide to SQLite (http://library.poisedsolutions.com/coding/database/the-definitive-guide-to-sqlite.xhtml). The index isn't great, but the book is a good read.

If you are not SQL literate, then perhaps not the best solution, but if you are SQLite is a great little database. SQLite is finding its way into lots of my projects. The database is just one file, little configuration needed (zero), good command line app, and quite simple to interface with programs.

[DanHarrison]

What immediately strikes me is that you probably want an online web-based database, which you just access with a web browser. If you don't want people to see the data, then you need strong usernames/passwords.

Forget syncing, I've done that before and it's a complete nightmare. A central system accessible from anywhere using a web browser will save you money, LOTS of time, and be very easy to use.

Dan

[MartCactus]

What immediately strikes me is that you probably want an online web-based database, which you just access with a web browser. If you don't want people to see the data, then you need strong usernames/passwords.

Forget syncing, I've done that before and it's a complete nightmare. A central system accessible from anywhere using a web browser will save you money, LOTS of time, and be very easy to use.

Dan

I'd agree with this - assuming both users of the database will have internet access.

Synchronisation can be complicated, especially where you have 2 or more users updating the data. Whereas with a web database you actually only have one database - so if I add a new record, that is then available for the other user. IF you have 2 separate databases that you synchronize, you have problems if you've both updated data - it has to decide (or you have to tell it) which of the updates to copy to eachother.

[FireFleur]

You synchronise by creating a third database, that has distinct row values combined from the other two.

I am beginning to feel like the masked magician :)

[Subbynet]

You synchronise by creating a third database, that has distinct row values combined from the other two.

I am beginning to feel like the masked magician :)

That's not sync'ing.. That's merging. When you sync, you keep two databases, you clearly have a third, and the third db will be different from both db1 and db2.

[NextPoint]

Keep it simple and use an online database. Massively reduces the risk of data accidentally being overwritten by old data or other complications that could occur through synchronising separate databases.

[FireFleur]

That is synchronising you synchronise two database to a third databases, which is also a merge :)

Synchronization has a time element to it, let's not go there, but watch ;):

a + b = c

a, b = c

just assign a and b to c.

[JohnGrove]

Two options come to mind, both of which I've implemented for clients.

If you have a network and a spare pc you can allocate remote desktop access to that pc and install a MS Access front end on it. The data backend would sit on a server/workstation within your network allowing you both to link to the live data.

The other option is to install an open source CRM solution on one of your machines. I support SugarCRM and would be happy to talk you through it.

[chapelman]

A big thank you to everyone for your ideas. I'm thinking that the online database option might be the way to go. I don't want to host it myself as if I am on holiday or out of the office and my PC goes wonky (technical term) then my business partner would be in the poo (another technical term) so because of that and the fact we have both used Google docs in the past I think I need to find a good, cheap reliable online database.

Any suggestions?

Anyone?

[DanHarrison]

Providing you had a data system developed for you, any standard web hosting service would do the job (one that has php and MySQL). There are some off the shelf packages for creating databases, or you can have one custom made for you.

So that I can help more, exactly what information are you looking to store? And what are you doing with that information? (Feel free to PM me if you don't want it public).

Dan