Building OOo forms for these usually requires the following :
Install a local copy of the db to my machine.
Build the form, save and test it locally. I save the form outside of
the ODB document.
Change the form to point to the identity and location of the remote
datasource (different passwords, different entry IDs, etc)
Copy the form to the remote file server.
Adjust the links on the remote workstations to point to the new form.
Register the corresponding ODB file with each workstation, which means
copying it to each workstation, otherwise the forms on the file server
lose their connection to the datasource. There is no way to share an
ODB stored on a file server and allow concurrent access to it. Things
get screwed up if you try that. This means that you have to write
protect the form, otherwise you get users answering "yes", to the OOo
question : "Changes have occurred in your document, do you want to
save them ?" For a user, it is totally illogical not to want to save
what they have just entered on their form and not save it.
Hi Alex,
Do you mind if I ask why you put the form on the shared file server,
stand alone. If you are pushing copies of an odb file to the
workstations why not just have the form embedded in the odb file?
So - you can update the form without having to update all the odb file?
Thanks
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
