To answer your second question first, no. (no, I don't do samples).
Here is the thing you need to consider: A form only exists in an opened state if it is in your workspace. Your workspace does not overlap anyone else's workspace because those workspaces are in the memory of the workstations, not in the shared database.
All forms are closed documents in the shared file that is your .MDB file. What each person will see is the document that is the form, either closed or open as a private copy only. So... the only way I know of to "chat" involves a rather little form that allows you to see individual records, probably in Memo format, with a source and timestamp. To add a chat entry, you have to post it to a chat table. The chat table has to record the entries in date/time order. BUT... if the chatting workstations don't have MS Time Services turned on and linked to the same domain controller, there is no guarantee the times will be the same from one user to the next. Therefore, the order of posting might be an issue. Ditto using an autonumber field, since the number is reserved before it is written. The order of clicking the "POST" button and the order of the autonumbers therefore are not necessarily strongly related.
The further catch is, of course, that you need to handle record locking issues AND you need to clean out old stuff on a regular basis. Otherwise, you will fail to post AND you will fill up a disk. Which is why it is far better to go buy a product designed for chatting in the first place. Why re-invent a wheel when there is already an after-market for them?
