Am Sonntag, den 23.09.2007, 03:01 -0400 schrieb Andrew Jensen: > See this is where not being able to reference a controls value to fill > a parameter in a query is a pain. > > What you really want is a list box that has two possible query > statements for its values.
Hm, sounds like scripting would be acceptable in this special case. I haven't tried, but changing the statement by code at runtime and refreshing the form doesn't look so difficult (read: should work). I did with form filters and that was easy to do. May I ask: how would this be done in competing db applications (msa, lotus approach, kexi)? > In one case it needs the all of the values from the Detail table, to > display the current values in the MasterDetail table. > In the second case when you are adding a new record you want the list > box to be filled with something like this: > > SELECT "Txt", "ID" > FROM "Detail" > WHERE "ID" NOT IN ( > SELECT "Detail"."ID" AS "ID" > FROM "Detail", "MasterDetail" > WHERE "Detail"."ID" = "MasterDetail"."DetailId" > AND "MasterDetail"."MasterlID" = ?) > > This was you only are shown the detail records not already assigned to > a particular Master record. That is pretty much the case of assiging rooms to events. I can imagine stumbling on things like that pretty often. I fear having a listbox like that will be rather complex to handle for the average base user. On the other hand it may be an outstanding feature ... that depends on the occurence frequency of use cases where it's applicable. Did you write an RFE yet? Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
