Jens:

What are you using to create your HTML pages?

>Michael,
>
>No, it was actually quite straight forward.
>
>I had to include these files in the wconnect project, in addition to my application’s data classes:
>
>Adodefs.h
>Cdata.vcx
>Cmdata.vcx
>Cmdataa.vcx
>Cmregkey.vcx
>Codemine.fll
>Codemine.h
>Codemine.prg
>Datadefs.h
>Win32.h
>
>If you don’t use Codemine’s Primary key generator I don’t think you need the Cmregkey library.
>
>I chose to create one abstract wrapper class where I create the connection to the cde object, set the path to the database and so forth. I have subclasses of the abstract class that more or less correspond to the different cursor classes in the cde. In the subclasses (which are used in the process object in wconnect) I store data in a oData property and / or return a cursor. What I really like is that it’s so easy to test these classes from the command window before trying to use them in wconnect.
>
>Jens Erik
>
>>Jens:
>>Was it very difficult to integrate Codemine and Web Connect?
>>Mike
>>>Hi Gary,
>>>
>>>>Hi Jens:
>>>>
>>>>Long time no see round here!
>>>
>>>Yes, it has been some time. It’s not that I don’t log on to the UT (I seldom get the “You have more than 400” message), it’s just that I don’t have all that much to contribute with...
>>>
>>>Also, I’ve been busy converting our main app from Cm 6.1 to 7.1 and trying to learn the new concepts. I’m really amazed with the new version, especially the new data classes. If just people knew what a great product Codemine is and gave it a try, I’m sure a lot of people would be impressed. I’m just finishing a brand new app where I’ve used Cm 7.1 from the start. This is a combined rich client / wconnect Intranet application (approx 1,000 users), and it’s so cool to be able to use new cde so easily in both environments. Right now I’m working on a small NT service app which also will be using the same cde.
>>>
>>>
>>>>
>>>>You should be able to get around that by specifying "Thisform.ContainerName.nColumn1" rather than "This.Parent.nColumn1".
>>>
>>>Yes, that should work. We found a workaround, but I’m still hoping for a fix here.
>>>
>>>Regards,
>>>Jens Erik
>>>
>>>
>>>>
>>>>Best
>>>>
>>>>
>>>>>Michael,
>>>>>
>>>>>This is because of the binding manager. When it sees This.Parent, it will try to look for the property on itself, and not on to the control we’re actually dealing with. Codemine has promised to change this in a future release. Then there will be a check if controlsource starts with “this.”, and it will then be replaced with “oThis” in the binding manager.
>>>>>
>>>>>I’ve been waiting for this enhancement myself. Maybe if you also send a request to Codemine support... :)
>>>>>
>>>>>Jens Erik
>>>>>
>>>>>>Thanks Gary:
>>>>>>I figured as much. Though this is probably a foxpro question, why can't I set the controls ControlSource = This.parent.nColumn1 for instance if nColumn1 is a property of the Container? It works for Thisform.nColumn1.
>>>>>>>Hi Mike:
>>>>>>>
>>>>>>>>Right now I've figure I must modify the container init
>>>>>>>
>>>>>>>To set the initial value of the container's properties.
>>>>>>>
>>>>>>>> and the controls afterchange to set and change these values.
>>>>>>>
>>>>>>>To set the subsequent value of the container's properties after the controls have been changed.
>>>>>>>
>>>>>>>Seems OK to me.