PB; COMate, ADOmate; parsing speed;
Posted: Fri Jun 26, 2015 6:39 am
Hello,
I am currently using COMate/ADOmate to access MS SQL Server and it simply works.
What I am curious about is the invoke command.
As I understood from reading the COMate source code, a call to a property or calling a method involves
parsing of a string message like
Interesting, not only the signature is parsed, but it seems the full statement has to be parsed;
so no way to prepare a statement and give it other arguments.
Maybe due to the fact the whole statement is parsed into a compact memory block in COMatePLUS_TokeniseCommand?
Accessing a database, that is fast enough compared to data access.
But what if I would use an ActiveX library for GUI purposes needing fast access for drag'n'drop, resizing, etc.
Is it fast enough?
Why is it done this way? (O.k., if there would be another way...)
I'd appreciate any hints and will read again through the chm document for COM during the weekend.
Thanks a lot
I am currently using COMate/ADOmate to access MS SQL Server and it simply works.
What I am curious about is the invoke command.
As I understood from reading the COMate source code, a call to a property or calling a method involves
parsing of a string message like
Code: Select all
COMate_PrepareStatement("Replace('The quick brown fox jumped over the lazy dog.', 'cat')")
so no way to prepare a statement and give it other arguments.
Maybe due to the fact the whole statement is parsed into a compact memory block in COMatePLUS_TokeniseCommand?
Accessing a database, that is fast enough compared to data access.
But what if I would use an ActiveX library for GUI purposes needing fast access for drag'n'drop, resizing, etc.
Is it fast enough?
Why is it done this way? (O.k., if there would be another way...)
I'd appreciate any hints and will read again through the chm document for COM during the weekend.
Thanks a lot