Access Specific DB Theory

[NewTexican]

I've just recently joined this post, but I've been scanning it for a while and finding it very useful.
I'm building my first complicated db. I don't have a programming background.

The whole of the db, user interface and tables, is on a server drive. The db is not accesed often, but a form(s) is probably always open by any assortment of users. There is approx 5 users. I don't want to burn too much time going down the wrong road.

Question: What would be the best way to construct how access manipulates the data? I can think of 3 general constructs.

1. Fewer queries and more forms/subforms that access the tables directly.

2.More queries and fewer subforms (more queries between form and table).

3. Unbound forms w/textboxes and subforms and more vb code.

The DB will be used mostly to look up information on people, companies and projects that are all related to each other in many to many relationships.

 

[MakeItSo]

I'd suggest using a main form with subform to display the basic informtion on people (contact details and most important info, e.g. company/department/special knowledge),
plus a main search form and a few result forms to query the db for more specific information.

Plus: I suggest consulting MS Access forums forum702 and forum705

Cheers,
Andy

[blue]The last voice we will hear before the world explodes will be that of an expert saying:
"This is technically impossible!" - Sir Peter Ustinov[/blue]

 

[NewTexican]

Thanks MakeItSo. I was looking for more specific forums. I hadn't drilled down to 702 or 705 yet.