PaulBarter
MIS
I have several different classes that access different databases.
All these classes use the same data structure to hold abbreviated details of the fields in the database which the users programs need to refer to.
This is defined as:
The problem is, when I use more than one of these classes in the same program, VB seems to get confused as to which one it should refer to.
e.g.
I can, of course, define them more explicitly by using qualification
but VB won't let me assign these structure to each other so I can use them in generic user routines
Without any qualification it seems to run sometimes ok under VB, but gives a complie error whenever I try to make the .exe
Is there any way round this?
All these classes use the same data structure to hold abbreviated details of the fields in the database which the users programs need to refer to.
This is defined as:
Code:
Type FIELD_ITEM
Name As String
DefinedSize As Long
Type As DataTypeEnum
End Type
Type FIELDITEMS_DATA
Table As String
Items As Long
Item() As FIELD_ITEM
End Type
The problem is, when I use more than one of these classes in the same program, VB seems to get confused as to which one it should refer to.
e.g.
Code:
Public gtypFieldData As FIELDITEMS_DATA
I can, of course, define them more explicitly by using qualification
Code:
Public gtypFieldDataA As ClassA.FIELDITEMS_DATA
Public gtypFieldDataB As ClassB.FIELDITEMS_DATA
etc...
but VB won't let me assign these structure to each other so I can use them in generic user routines
Code:
gtypFieldDataA = gtypFieldDataB
Without any qualification it seems to run sometimes ok under VB, but gives a complie error whenever I try to make the .exe
Is there any way round this?