Search results

Thanks @cheekybuddha , very helpful. Believe me not wanting to run, just trying to grasp the basics but spinning out of control lol.

Thanks @cheekybuddha, it works in PostgreSQL - direct from tutorial mentioned in specific area of Multiple Rows & Multiple Fields area of subqueries Youtube techTFQ titled "Subquery in SQL | Complete SQL Subqueries Tutorial". Thanks for your input on the qry. I just cannot see how I can learn...

Think I've ran into another flaw between native SQL & Access SQL. Access will not allow Multiple Row & Multiple field subqueries. Reluctantly I may have to quit the native SQL tutorials on Youtube techTFQ as it seems near unrecognizable in Access. A multiple row, multiple column subquery seems...

Thanks people., much appreciated.

Thanks @plog, interesting that the prompt from Access is incorrect; should have warned me about the join statement not 'FROM clause'. Grateful for the input on Alias' shorthand only in FROM clause.

Thanks @The_Doc_Man, I do not blame you for not downloading. Pasting in Notepad & Word I can't see any unexpected phantoms. I didn't have a primary key in one of the four tbl's as one of the tbl's didn't have an obvious PK (not related to this query). Putting a PK in said table (unrelated to...

A brilliant SQL resource on Youtube tachTFQ (great teacher) - BUT exactly how different is native SQL compared to ACCESS SQL? Richard Prost does not indicate a great difference & I would have thought semantically it would be near identical. Seems to have different datatypes, ∴ data-sizes...

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...