Saved query Vs SELECT property
On my MS Application application, I have several forms containing combo-boxes (as some of you know from your help last week :O). Currently, most of these objects have the rowsource set via a SELECT statement in the properties. My question is this. Is there any real benefit in converting those SELECT statements, to saved queries?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
There are also times when I modify the SQL of either the form (search form results), or the combobox (cascading) alot through code. In those cases it doesn't make much sense to me, to use a stored querydef.
Another reason why I sometimes prefer NOT to use a stored querydef object is that I don't want it to clutter up the navigation interface while developing.
Another reason why I sometimes prefer NOT to use a stored querydef object is that I don't want it to clutter up the navigation interface while developing.
ASKER
Thank you everyone.
ASKER
Thanks everyone - have a great week.