Douglas,

>Anyway, are you saying that we will have to wait until the next release to even try to use event objects?>

No, what I'm saying is the Event object in its current incarnation works fine...The original concept of the Event object was a good one...However, the implementation and the developer interface need a bit of "gussying" so that it is more intuitive and easier to use. The difficulties you are experiencing understanding how to use it are typical of what I have seen others experience...thus the need to clarify the interface.

>As an example, rather than have a form open up the business objects and associated data, I thought (since the Event object will instantiate any biz objects not already in existence) I would just pass the entity array listing of the biz objects in my CreateObject call(see page 63 of the Dev. Guide). There is some code in the cBaseEvent.ValidateExistingObject...Array method which fails on my array biz objects. The code is checking the second element of the array and if it's type is not "O", then it returns F. Now, the element in question is of type "C" and I cannot determine how to get it to be an Object type, especially if the object does not exist yet and, therefore, would not be instantiated yet. I went back and placed all my biz objects on the form, and the results are the same.>

As mentioned in the Developer's Guide, the first column of the array you are passing in the CREATEOBJECT command should contain the name business object. The second column of the array is used to store an object reference to the business objects...if they already exists...In your case they don't, so you can simply leave column 2 of the array blank which will make the TYPE of that column Logical.

P.S. Have you ever recovered from the "um...Lisa" faux pas?