I didn't realize until this project that all of my relational database
work was kind of one-dimensional, all of the related tables were built
with dropdowns to feed the main table in mind. None of the related
tables update information by users.
Now I have a project where I need to add several
to add a try and catch for error handling.
HTH
Michael Traher
Systems Manager
ICLP (London)
-Original Message-
From: Rick Kennerly [mailto:[EMAIL PROTECTED]
Sent: 02 September 2003 13:54
To: CF-Talk
Subject: Mutiple SQL Inserts
I didn't realize until this project that all of my
I don't get it about your db design/structure.
Let's call Main Table (Parent) and Related Table(s) (Child/Children).
In that case, a child is dependent on its parent and the degree of that dependency
(cardinality) is determined by the relationship (chiefly mandatory or optional).
Therefore,
If you're using MS SQL Server 2k you can use an identity
column in the related table and use the scope_identity()
function to return the value inserted into the column from a
stored procedure. That's the most efficient way if you're
using SQL Server 2000...
If you're using Oracle or another DB
]
Sent: 02 September 2003 13:54
To: CF-Talk
Subject: Mutiple SQL Inserts
I didn't realize until this project that all of my relational database
work was kind of one-dimensional, all of the related tables were built
with dropdowns to feed the main table in mind. None of the related
tables update
Isaac said,
The problem with multiple form pages is that they tend to
piss users off... they want everything on one page
This is *so* very true I just had to jump in. I had a client with large
forms and lots of traffic (insurance quotes and applications). All but
a very few of the competition
6 matches
Mail list logo
