Hmmmmmmmmmmmmm,
For ONE, the 'Seek' issue is NOT quite that simple. You cannot use the 'Seek' on a n'on-native' table -AND- Ms. Access considers all 'Linked Tables' to be non-native, even if they are just in a different ".MDB" file. However a Table in an 'OpenDataBase' object may be considered as a native db, and thus the seek method will work on these tables. On the other hand, If you are using the seek method, you know wnough about the record(s) you are accessing to generate a recordset of the records (via 'query') and thus the whole issue should be a non-starter in the concerns race.
Another whole universe of issues is certainly addressed in the numerous references provided by Terry, I would urge you to thoroughly review these.
One aspect which I feel is not well covered is the actual planning estimates for the load. Do you HAVE projections of the recordcounts for the various tables? Do you HAVE a head count of expected users? Do you HAVE any control over the 'growth' of the number of users? Do you have db security in place. As the Amex Ad says "DON'T LEAVE HOME WITHOUT IT". Even if the "boss" says 'no' -"DON'T LEAVE HOME WITHOUT IT". Check, ctrosscheck, recheck and double check with the net cops in your neighborhood. MAke sure your app settiings and the net settings are properly setup and coordinated and optimized for database applications. The default settings for almost ALL networks are targeted towards the generic office suite. File sharing for (small) documents, a few spreadsheets, some presentations. Printer sharing, e-mail and often for internet/intranet 'surfing'. NOT database operation. It IS different. Most of the local 'net cops' I have met do not even know there is a difference, many do not know what 'settings' are available. You need to tread lightly on their toes in most companies (they are generally considered 'better' than you)-BUT you do need to tread on their toes, at least until you are sure they KNOW about the differences.
More on the network situation. If AT ALL possible, any ane every non-trivial db should be on some server which DOES NOT deal with e-mail and or internet access!!!!!
While not explicitly part of the sharing process, you should carefully check that the db is reasonably normalized and that proper relationships are established before 'going public'.
MichaelRed
mred@att.net
There is never time to do it right but there is always time to do it over