MagicFrisbee
Programmer
I have designed a COM Server on paper. It will create, edit, and delete object rows in a database. We access our AS/400 databases using BDE.
So, what's my best strategy? Should one DataModule be created for the COM library? When would I create and free it? If I set up my objects with ciMultiInstance and tmApartment parameters, are calls to my datamodule thread-safe (like, can I do a FindKey and 100% expect the next line to be reading the row I found with FindKey?)
Or do I have each object own its own DataModule. Wouldn't that create havoc with the BDE having so many clients?
Dephi documentation is good at explaining COM and good at explaining data modules, but no good at explaining the two technologies put together. Any tips or experience would be appreciated.
"Roj"
GIS Programmer
City of Orem, UT
So, what's my best strategy? Should one DataModule be created for the COM library? When would I create and free it? If I set up my objects with ciMultiInstance and tmApartment parameters, are calls to my datamodule thread-safe (like, can I do a FindKey and 100% expect the next line to be reading the row I found with FindKey?)
Or do I have each object own its own DataModule. Wouldn't that create havoc with the BDE having so many clients?
Dephi documentation is good at explaining COM and good at explaining data modules, but no good at explaining the two technologies put together. Any tips or experience would be appreciated.
"Roj"
GIS Programmer
City of Orem, UT
