sysobjects table?

[brightstar]

ok, ive seent hese for bloody ages... and ive always found that a good compact and repair, or at most transplanting the objects from one database to another, gets rid of them.. but what he hell are they???
if you look in sysobjects table in any version of access you get the proprties of the object.. but along with these records there's loads of these things:

~sq_cFrmNewCall~sq_cCmbCompany

there can sometimes be loads of them... what the hell are they?i check out the text boxes and comboboxes that they refer to and cant find anything wrong with them.

http://www.agonyonline.co.uk

free, anonymous advice provided by the whole world

 

[dhookom]

I believe they are temporary cached Row Source and Record Source SQL statements.
The one you mention is the Row Source property of the combo box cmbCompany that is on the form FrmNewCall.

I believe they are a method of optimizing form and report efficiency when objects are not based on saved queries.

Duane
MS Access MVP
Find out how to get great answers faq219-2884.

 

[brightstar]

well that makes sense.
so which is best?
setting the control source of combo boxes to a SQL string, or a saved query?
honestly ive always created my combo boxes using the query builder and then left it at that, never thought of actually saving it as a query.
is there any design/performance differences?

http://www.agonyonline.co.uk

free, anonymous advice provided by the whole world

 

[dhookom]

I don't believe there is much of any performance difference since there are these "ghost" queries that get saved. I always use row sources of sql statements. I find a form becomes more stand-alone this way.

Duane
MS Access MVP
Find out how to get great answers faq219-2884.