=?Utf-8?B?Z29sZmlucmF5?= wrote
in :

Unbound forms are not less complex, but MORE.

Very true -- you have to put in a whole bunch of code to replicate
features and events that you get without code in a bound form.

Having to set recordsources on
the fly is something you should avoid.

Why? I see absolutely no reason to avoid it. Indeed, I'd say it's
the first choice for any form.

Bind the forms to a table or query

Terrible idea -- it may work with small tables, but quickly becomes
inefficient. It's also very bad if you try to upsize it.

then when you upgrade the sql it will be easy to set the links.
Google unc paths to find out how.

UNC has zilch to do with the subject of bound/unbound.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/