could this be done with MsAccess

[sparks80]

Setting up the tables and the relationships between them should be quite straight-forward for what you need.

I think the challenge will be displaying the records in the exact format you want. It should be possible, but is quite a big ask when you're starting out with Access.

I'm more than happy to help as you go along.

 

[squarebanana]

thanks for that sparks i have included a screenshot of where i am up to with it, just so you know where i am coming from, i would like ot get this on the server box i have then get it up and running the only trouble is i would have to have all the PC's at work on a domain and set the server up as a domain controller so all the PC's could log on to the network, But the only problem i have with that is that the linux fileserver and the main print PC would have to remain seperate as if ever there were a database or computer domain problem, the main print PC would have to stay online, so that's something else i would have to sort out.

Alan

 

[sparks80]

Hi,

The networking issues may well be beyond my expertise - but I'm sure the friendly folk here will be able to assist.

If you have multiple employees viewing and modifying the data then the backend database will have to reside on the file server where it can be seen by all employees. Maybe you could then set a scheduled task to regularly back up the database table onto the main print PC?

Mark

 

[Lightwave]

Squarebannana usually building the tables is actually very quick and there is a knack to understanding relationships but once you get a hang of it you can actually understand the basics of most structures very quickly.

Networking is a complicated subject and not really a subject of this forum but setting up a split database on a network that already exists is very simple.

Now once you get the hang of those things most of your time will be taken up designing the forms so that they are intuitive and making the forms flow in the same way as your processess. Most processes have exceptions and these can be very tricky to fit into work flows. Its a bit of a black art having the exact right fields layed out in a nice flowing style.

Every now and then even once you've got more competent an exception to a process or something you have overlooked will require you going back to add fields to a table. Occasionally it will require a complete redesign of the tables which can be very awkward but the more competent you get the less likely additional fields will require a complete structural redesign in which case adding fields to existing tables is an irritation rather than a big problem.