DATATABLE v4 (OpenInsight Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== DATATABLE v4 (OpenInsight Specific) ====
=== At 03 SEP 2000 06:31:28PM Matt Crozier wrote: ===
 
{{tag>"OpenInsight Specific"}}
 
<QUOTE>
Jim, Don, Carl -



We've found that using version 4 of DATATABLE.DLL fixes a problem we have with populating the control, however them seem to be other drawbacks using version 4 with OI as indicated elsewhere here.  Specifically with synchronization between DEFPROP and the control itself, and with some event co-ordination).



Has anyone implemented version 4 of DATATABLE.DLL and successfully found and worked around the problems of using this with OI?  How difficult is it to get this going?



Thanks - Matt.
</QUOTE>
----

=== At 04 SEP 2000 12:23AM Don Bakke wrote:  ===

<QUOTE>Matt,



We have not tried v4, just v3 with minimal success.



I am curious about your comment that v4 fixed a problem with populating a control. Did you have a problem with v2 (i.e. the one that ships with OpenInsight)? What did you gain with v4?



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]

[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 04 SEP 2000 04:31AM Matt Crozier wrote:  ===

<QUOTE>Don,



Yes - with v2 we had a problem with sending an INSERT SendMessage to a (virtual memory) edittable whose display area (ie, number of cells) on screen exceeded a certain limit.  If the edittable was it's normal size on screen, it could be populated - but if it was maximized with it's parent window (increasing the number of visible rows), the INSERT message would return happily but with no result either on screen or in DEFPROP.  With v4, this doesn't seem to happen - I guess 'cause it handles memory better.



I haven't tried v3, but the problems you were having in a previous thread sound similar to what we were getting.  It may be easier trying to resolve the problem above by accessing DATATABLE.DLL v2 directly somehow?



Cheers, M@

</QUOTE>

----

=== At 04 SEP 2000 08:52AM Don Bakke wrote:  ===

<QUOTE>M@,



Well the problem is that if you use the v2 DLL then you are using the v2 edittable. They are both one and the same.



The other problem is that datatbl.dll is actually called by a another DLL that Revelation uses as a shell: editable.dll. Herein lies, I believe, the biggest problem. This shell is specifically written for v2 and would have to be rewritten in order for OI to work very happily with v3 or v4.



I suppose this is what the CSP (Collaborative Source Program) can be good for...assuming you know how to write C++.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]

[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=40BB6C2424CC76098525694F007BBB11|View this thread on the  forum...]]