Hello,
        Using TrueDBGrid prerelease from Apex Software Corp. 16-bit version
        with Visual Basic 4.0 Enterprise edition.

        I get an OLE AUTOMATION ERROR occur with the following code:

        Sub TDBGrid_LostFocus()
                if (TDBGrid.Columns(3).value <> "") then
                        datacontrol.UpdateRecord
                end if
        End Sub

        This is what happens:

        If I am on the grid, I enter a new record, and in between, I decide
        to cancel my changes, I hit the Cancel button, which causes the Lost
        Focus event to occur for the grid and then I get hit with an OLE
        AUTOMATION ERROR (-214718342234 (-8c00f) ) etc...garbage I take it.
        The Value in Columns(3) is undefined, I have not gotten to it yet
        when I hit my cancel button.

        Can anyone help?  All I wanna do is make sure that the 2 or 3
        fields I need filled, are filled in, and then I don't mind the
        record being added.

        Any help would be much appreciated..

        Thanks in advance.

Deepak

The comment I got from Apex was: "don't use Truegrid with VB4". Be vely vely
callful when using it... !

The mega-problems I had when using it were:

  1) in Callback mode, if anything returned Value=NULL, it whould
     just kill the rest of the output to the grid after that.
     (last line in the Proc: 'If Value = NULL Then Value = ""' works.)

  2) In DB-Mode it would sometimes just not show the value contained
     in certain fields / records. No Idea why. (Hey, I'm just a
     programmer, not GOD!)

  3) In DB-Mode the SEEKs and FINDs on the Datacontrol just don't work.
     Suggested Workaround: to work with a Clones Recordset and pass the
     Bookmark to the Datacontrol (Neat. Just double the Overhead.).
     Since I usually work on small Subsets of the actual Data I just
     "MoveFirst" and "MoveNext" until I'm at the right position. (I
     thought this would be better than dBase III. Oh well.)

Since the Grid on the whole DOES work (at least better than the DBGrid in
VB4), I still use it. As soon as the Boys over at Apex get to patching the VB4
Bugs, I'll happily use it alot (or do they have to wait for Microsoft to patch
the VB4 Bugs?).

Jo

Wow, we got the same message when we tried to do something relatively
different. Ours occured when we tried to pass a record source to a
data control on a remote client.

Silly us: we thought that distributed didn't mean ODBC configurations
on 250 remote workstations.

We called Redmond and I could tell right away that they had never
considered the possibility that we might want put a data control on a
remote client without having JET installed on each and every machine.
In other words, they were no help. The short of is that we figured
that the data control and DAO have a hard time being encapsulated. In
any event, go to WWW.APEXSC.COM (makers of dbgrid thingy) and download
a new version (16 and/or 32) and see if that helps.

Sorry I rambled.
Leighton