Conference utrop1::linkworks_v3

2192.0. "Another OLE problem, this time VB 4 on Win95" by ESME::SPENCE (Bugs? You mean insects?) Thu Apr 10 1997 19:58

Hi - because of the problem mentioned in topic 2190, I switched
my client development to a Windows 95 platform. Part of my VB
application has code something like:

	.
	.
    ObjClass = ThisSWC & "IntelLog"
    rc = CurObj.ImportNewObject(NewObjRef, _
                                ObjClass, _
                                "On " & txtName.text, _
                                "AccRtPublic", _
                                Filename)
    Set NewObj = lnx.GetObject(NewObjRef)
    ' Set the HasFirearms attribute according to the data we found.
    ' We use one of the address fields to determine this.
    If Len(txtAddress.text) > 0 Then    ' If there was firearms info...
        NewObj.HasFirearms = True
	' I've already set up an alias for this
	.
	.

Now I have an object class derived from 'Note', called 'IntelLog'.
I also have an attribute called 'HasFirearms'. The first I tried this,
I'd forgotten to assign the attribute to the object class, and so
when I executed the line

	NewObj.HasFirearms = True

then I got an error back saying that the object doesn't support this
property or method (the ImportNewObject before it was successful, and
the object got created on my desktop).
Fair enough - that was my mistake. So, I assigned the attribute within
the workbench, committed the change, ran the application again, and now
the ImportNewObject method fails! When I try and import the object, I
get a dialog box entitled 'Microsoft Visual Basic' with the contents:

Run-time error '-2147353567 (80020009)':

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 't5f5e11b'.

This looks to me like a bug! I'm running out of platforms on which I can
build this demo!

I'm using the same LNX server as before (see topic 2190), with Windows 95,
Visual Basic 4.0, Visual C++ V4.2, DCE V1.0, LinkWorks 3.0.8 (Dec 96)
on the client.

Any ideas? I'm sorry I keep throwing up all these problems - but I bet you'd
prefer this to us not using LinkWorks ;-)

Cameron,

Did you CommitChanges in the Configuration Manager after the attribute assignment?
This is typically the message you get when the atribute table is not yet created
in the cell and you try to create an object of that class.

Regards,
Jos

(have to find VB5 for NTA...)

Hi - I've recently rebooted the system, and the problem seems
to have gone away. I guess this looks like I forgot the commit
changes - sorry!

On the subject of Alpha kits - I've now got both Visual Basic V5
and Visual C++ V5 for Windows NT/Alpha - both for free - off our
own network. The notes conferences for them are:

Visual C++ on Alpha:	DECWET::VISUAL
Visual Basic on Alpha:	DECWET::VB-FOR-ALPHA-NT

They take a long time to copy across the network, being
several hundred MB each. Well worth it, though. The Visual
Basic one produces native AXP code.