bb.donnay-software.com

Michael - Your posting triggered my memory about a problem I had when helping a customer (Bobby Drakos) with a big problem he was having after a dbGoTo(). We found that the value of the fields did not always load unless we skip off the record and back onto it again. This was causing multiple records...

Ok, now I'm starting to understand more about your problem after running the sample. It appears that this OCX is meant to run as it's own dialog and not as a control on another dialog, therefore your original code seems to be best and I have removed the @ DCACTIVEXCONTROL command because it fails to...

I will create a sample program today and try to help you with your painting problems. Some OCX controls behave differently than most. I have never had a problem putting any other OCX on a dialog window in the past, but let me see what I can do. I have often seen better results when putting the OCX o...

Pablo - I am interested in why your aliased functions ( example: @sqlite3:sqlite3_column_name(stmt,n) ) seem to work properly whereas DLLFUNCTION can produce IDSC's and wrong returned values. This causes an error because it returns a numeric instead of a string: sqlite3_column_name( stmt, 2 ) DLLFUN...

Ok, now I understand.

I just need to figure out what event gets fired when that CLOSE button is clicked.
Then I can subscribe to that event and send another event to the parent window to tell it to close.
There are other workarounds that would probably work too but too much guessing.

Your question is confusing. If the dialog window is the PARENT of the ActiveX window, then you can't hide it behind the ActiveX window or make it smaller than the ActiveX window. I don't know what events occur when you try to close an ActiveX window. I never do that. Instead, I close the dialog wind...

Don't close the EasyIntegrator window, instead close the dialog window.

If the EasyIntegrator window is a child of the main dialog window, it will automatically close.

Build 254 is a maintenance release. Use the download and password information given to you previously for build 253. ---------------- New to 1.9 (build 254) ---------- 1096. Fixed a problem with tooltips not displaying correctly on a secondary monitor when using dual monitors. 1095. Fixed a regressi...

Build 254 is a maintenance release. Use the download and password information given to you previously for build 253. ---------------- New to 1.9 (build 254) ---------- 1096. Fixed a problem with tooltips not displaying correctly on a secondary monitor when using dual monitors. 1095. Fixed a regressi...

You need to call the code in the EVAL clause of DCREAD GUI. DCREAD GUI EVAL {||InitControl(oEasyIntegrator)} RETURN nil FUNCTION InitControl( oEasyIntegrator ) LOCAL trans, oCustomer, oCustfields, StringSavedCustomerRef, cip_id oEasyIntegrator:LoadSetup(SetupString) trans := oEasyIntegrator:getPrope...