Stephen Russell wrote: > Backend Data will be SQL Server. > > BOM Bill of Materials for all who didn't know. In reality I am > creating a list for this weeks "Sex Offender Report" My user has a > table of all the law codes on the books and has to pick which ones > apply to this Sex Offender query. I capture the IDs for these Codes > "39-13-502" "Aggravated Rape" and put them into a table for later use. > > My Q is best way to work with this table and the collection that my > users define/redefine. In my testing today I get a collection of 60+ > codes when the user is looking for the proper Codes. They have a > check box in a grid and check any that pertain to finding someone who > has broken a law that the Sex Offender Report should show. > > So collection is 60+ deep do I > 1. Fire off a query per row knowing I need to add it, or remove it.? > 2. Union all Marked rows into one "Add" statement and union all > unmarked "Deletes" into another? > 3. Delete all in list then add in any that were marked? > 4. Got a different approach that I have not thought about yet? > > > > Hi Stephen. We have been working with BOM's in agribusiness and electronics assembly, both of which require dynamic and recursive capabilities. That said we have not been SQL orientated and use it only for straight forward reports.
Treating SOID as the BOM and COID as the ingredient in ordinary DB tables, with parent child, your form with tick boxes will easily drive the building of the result cursors of the SOR, and allow the user to rework results and revise judgements as to choices , to make allowances for equivalences in other contexts (substitutions & recursions). The dynamic element comes from the fact that COID applicability will eventually be seen to overlap and even vary, via Case History Dependancies, for example. So SOR's may benefit from a recusive capability. System design is also about future sales. William. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
