Doug - I use this method when the user needs the child tables on the form to have a WHERE clause. I just create a one-table view with the WHERE clause and use the view in the table for editing.
As an example, a client wants their consulting staff to have the ability to add/edit timesheet details for only their hours, but the accounting staff needs to enter timesheet records for expenses - into the same timesheet table - so each has a different WHERE clause on the timesheet details table. Sami ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sami Aaron Software Management Specialists 913-915-1971 [EMAIL PROTECTED] -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Hamilton Sent: Sunday, February 20, 2005 10:34 PM To: RBG7-L Mailing List Subject: [RBG7-L] - Re: DBGrid Form Whoa! That was a subtlety I hadn't thought about: If you have a number of single table views in one form, linked by aliased columns, then are each of the views (well, really, the underlying tables) editable? Is it only when you combine two or more tables into one view that they aren't editable? So, if you can edit a number of single table views in one form, then my idea of defining linking columns in a form among multiple tables is a moot point - just use the views. Thanks for your r:esponse, Razzak. Doug A. Razzak Memon wrote: > > At 08:13 PM 2/20/2005, Doug Hamilton wrote: > >> How feasible would it be to allow us to define the linking >> columns between tables in the form definition, probably under >> Tables | Add/Remove Tables. That way we could link tables on >> specified same-named columns. We could also link tables on >> differently named columns, much like we do in WHERE clauses. >> And since we'd be working directly with the tables instead of >> views, the data would all be editable. (I'm assuming multi-table >> views are not editable.) > > > > Doug, > > How feasible? > > Just remember, we can do R:Anything http://www.ranything.com > and R:Everything http://www.reverything.com > > Meanwhile, if you simply define a single table view as > explained in my earlier reply with two examples, and then > use those views in a form, you should be able to edit any > single-table view. That way you never have to tinker with > the original (not normalized) table(s). > > Very Best R:egards, > > Razzak. > >
