Subject | Whats really happening with tibotables ? |
---|---|
Author | rodbracher |
Post date | 2002-01-10T06:24:45Z |
Hi
We're doing a paradox to ibotable conversion D5 - IB4. IN our app we
had a few datamods with many active ttables on app creation. This
worked fine with paradox but converted to ibotables a sudden
reduction in speed of startup.
Cleary our model has to change - but I just want to know what each
active tibotable is doing as the app is created. What data does it
send to the client ( since an active tibotable is essentially
a 'select * from' ). When I watch the SQL monitor I do not see tons
of row data - So is there maybe data buffers prepared on the server
side ?
I also noticed it is the tables with the most no of fields ( not the
most data ) that take longer to load up.
Thanks - Rod
We're doing a paradox to ibotable conversion D5 - IB4. IN our app we
had a few datamods with many active ttables on app creation. This
worked fine with paradox but converted to ibotables a sudden
reduction in speed of startup.
Cleary our model has to change - but I just want to know what each
active tibotable is doing as the app is created. What data does it
send to the client ( since an active tibotable is essentially
a 'select * from' ). When I watch the SQL monitor I do not see tons
of row data - So is there maybe data buffers prepared on the server
side ?
I also noticed it is the tables with the most no of fields ( not the
most data ) that take longer to load up.
Thanks - Rod