>I have a question regarding the best strategy to use for a multi-user LAN application.
>
>In my app, up to five users will be using the same form to enter data. What is the best
>way to to open up the tables (shared) up to five times simultaneously.
>
>AL

Surely, tables will be opened in shared mode. Other things relate to interface design. The main question here is following: will your users like to edit the same record simultaneously. If answer is 'not': you have choice to use either pessimistic buffering or non-buffering, lock design. If answer is 'yes', then next question is coming: should users be aware of the changes another user makes to the same record in the same time. If answer is 'no', then use non-buffering, non-lock design. If answer is 'yes', use optimistic buffering.
You see, the good part of the job is to collect right user's opinion. From my experience, I would say that 90% of users don't like to edit the same record from different workstations, therefore I like non-buffering, lock design.