Montrose: Thanks for the great advice (many-tomany relationships using one table to store all IDs).
Can you (or anyone else!) help me with one more thing... I am writing a database in Access, then a layer of objects in VB to make using my database and writing applications for it much more "high level". Is this a good idea or will it just create a performance bottleneck? I am creating each table as an object and making certain parts visible through the objects - then representing each record as an object in a collection - thus making a "tree like" structure.
I am accessing the database using ADO through ODBC - is this a good idea!?
My final hope is to create a set of objects that makes coding an ASP frontend to this database very simple and many other programmers will write links in to programs such as Sage, Word etc etc etc.
I just need to know if this is a good way to develop things - and are there any things I should be watching out for?
TIA,
Jason.
Can you (or anyone else!) help me with one more thing... I am writing a database in Access, then a layer of objects in VB to make using my database and writing applications for it much more "high level". Is this a good idea or will it just create a performance bottleneck? I am creating each table as an object and making certain parts visible through the objects - then representing each record as an object in a collection - thus making a "tree like" structure.
I am accessing the database using ADO through ODBC - is this a good idea!?
My final hope is to create a set of objects that makes coding an ASP frontend to this database very simple and many other programmers will write links in to programs such as Sage, Word etc etc etc.
I just need to know if this is a good way to develop things - and are there any things I should be watching out for?
TIA,
Jason.