Search results

Thank you all for your input, massively appreciated. Sorry @arnelgp, this solved it. I posted at a hectic time & forgot to convert the subqry on the margin% field to a dLookup. The interesting question is WHY does a dLookup solve this. The subqry seems near identical in it's format. Why did I...

Thanks both for help. I changed the subquery to a dLookup fn using the query designer (which I would imagine it yeilds the same result as altering the SQL) & sadly the recordset remains uneditable. I know the issue is caused by The qry is used in a form but also used in other uses so i need the...

Thanks @cheekybuddha. I'm unable to post links with SPAM restrictions. Do a search for "Using a Subquery in a SELECT statement; red-gate "Simple Talk by Greg Larsen". I think there are instances where a basic subquery will yeild a single result... 'set as a column value' if I'm interpreting it...

Thank you @arnelgp. Is dLookup evaluated only once? Then echoed on all the rows? If this is the case then I see it wont' be much of an issue however if the dLookup is used on each row instance then that will be considerably slow.

What technique can be used when returning a single value used as the entire field in a qry (Field 3; populated by a subquery) whilst also maintaining an editable recordset? (SELECT TendersT.[Margin%] FROM TendersT WHERE (((TendersT.Current)=True))) I have no relationship between the tables/...

Thank you @moke123

Thanks @cheekybuddha

Everywhere I have read says to use the .ItemsSelected property of a listbox to obtain the value. Looping through on multi-selections. On a single selection listbox it seems that referencing the listbox itself will return the bound column value. Also if there is nothing selected it will return...

Thanks @The_Doc_Man. @Pat Hartman, not trying to be argumentative here at all, for my clarification: How am I misinterpreting you here - so in my mind the below contradicts this: I have defined an alias AREA, used a reference to that alias in the same query in VOLUME; without repeating the...

Thank you both, I'm doing myself no favours in panic posting & making silly errors. @Mike Krailo just bought the first two in your referred link (many thanks).

Any recommendations?

Sorry, no need to reference the object itself in the same query. But I would've thought it would allow it though as I would've thought being as explicit as possible is a good thing usually.

Thanks, I typed it in on the Query Builder thinking as i was referencing an object/ class (table/ query) in trying to avoid the annoying <<Expr>> labels which appear when transferring from 'Expression Categories' & loosing a lot of time navigating. So in using dot's instead of explanation points...

Thanks @June7, yes I thought so & thought it was erroneous. I hadn't messed around with the SQL at all so this was created by Access or more likely thanks to @cheekybuddha pointing out my bad reference. Ok makes a bit more sense. Do I need to look out for anything regarding unknown values not...

Thanks Dave, how embarassing :eek:.

Thanks Dave, it was merely a test in trying to understand what's going on at a basic level. Surely on something so basic it is capable within the Access Query Designer itself & not necessary to alter the SQL. Grateful for the input & I can see what's happening with the SQL but I'm trying to see...

Thank you both for your input. Creating a simplified test this morning (attached); calc'd fields in CAPS with a simple e.g. AREA based on tbl values & VOLUME dependant on the query result: @plog thanks for the detailed explanation. I must not be following you completely as if I'm interpreting...

Am I wrong here (usually am) - It seems in a query a calculated field (residing in that query) will require a subquery to be used if you reference the query name in the formula: AliasName: [QueryName]![CalculatedField1]*[QueryName]![CalculatedField2] Whereas if you reference the field itself...

It's tempting to hide behind the more technical issue & save face. But I have to be honest - I was referencing the field incorrectly of the record source. Got very confused with sub form referencing & I don't even think it was needed. I was not referencing a control on the form as I'm trying not...

Thanks Pat, sure enough I missed something :p.