Hi!
The problem is more simple. The idea is generate 1 copy of the
browsing program for each table that the guys of production
department will need to access. We are testing programs that was
converted from a 4th tool of mainframe. Then I have developed various
little programs to aid these guys. Programs will use components to
connect to DB2(SQLQuery, SQLTransaction, TODBCConnectio, etc) and two
visual components: A DBNavigator and a DBGrid. This is all!
Actually the trouble here is that updates to DB2 tables(at least with
the ODBC I have here, furnished by IBM I suppose) are generating an
empty MessageDialog and the program is cancelled.
Is simple like this! I didn't write any code(RAD tool. Remember!).
The table name is typed directly in the SQL property of TSQLQuery.
[ ]
Ricardo
At 18:02 29/3/2006, Matthijs Willemstein wrote:
But then again to use the same component i.e. a SQLQuery for more then
one operation is a bad design anyway. The only case I can think of you
can come away with this is on some form where you are editing base
tables. For anything else you should use separate SQLQueries for each
table you want to work on.
As you are programming for a procedural program, but event driven you
can never know where a certain SQLQuery is used for at that moment. So
if you change the SQL-statement of the query some strange things might
Happen, leading to very hard to find bugs.
Matthijs.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
