I have a UDT, addField, in a module, modBase, that is declared with Public
scope.  I am using it as a return type of a Public function in a form,
frmSLIC_report.  When I try to compile the program, I get the error:

Compile error:
Only public user defined types defined in public object modules can be used
as parameters or return types for public procedures of class modules or as
fields of public user defined types.

I feel like I meet all of these criteria, having a Public UDT and using it
as the return type of a Public function.  What's up?  I really need to get
some progress on this app and it's hard to show progress when it no longer
compiles!

Thanks in advance,
Chris

Show quote Hide quote But the UDT isn't defined in a public object module; BAS code modules aren't
public or objects.

Show quoteHide quote

Show quote Hide quote A form's not a public object module. UDTs are a pain imo. Someone that uses
UDTs once in a while may pop in with a "cure" but, imo, the fastest, easiest
and best way to fix it is to get rid of the UDT and use a class module
instead..

Converting a User Defined Type to a Class Module
http://www.vbsight.com/UDT_Class.htm

The error is not referring to the module-level UTD declaration of addField,
but rather that the scope of the procedure that returns an addField UDT,
when defined within a form, must be a private procedure.  It's the Public
scope for the procedure that's causing the problems. Basically it's saying
you can not define a UDT as public within in a module then try to have a
private entity such as a form return a the defined UTD.  You can pass a
variable declared as the UDT to the private procedure, and then that
procedure can be declared Public.  Or, you can return the UDT from a Public
procedure located in the same or another BAS module.

'BAS MOD
Option Explicit

Public Type addField
   field1 As String
   field2 As String
End Type


'ANOTHER (OR THE SAME) BAS MOD
Public Function aPublicBasProcedure() As addField

   aPublicBasProcedure.field1 = "filled in a"
   aPublicBasProcedure.field2 = "public BAS proc"

End Function


'SOME FORM
Option Explicit

Private Sub Command1_Click()

   Dim a As addField
   a = aPrivateProcedure()
   Debug.Print a.field1, a.field2

End Sub

Private Sub Command2_Click()

   Dim a As addField
   Call aPublicProcedure(a)
   Debug.Print a.field1, a.field2

End Sub

Private Sub Command3_Click()

   Dim a As addField
   a = aPublicBasProcedure()
   Debug.Print a.field1, a.field2

End Sub


Private Function aPrivateProcedure() As addField

   aPrivateProcedure.field1 = "filled in a"
   aPrivateProcedure.field2 = "private proc"

End Function

Private Function aPublicProcedure(af As addField) As Boolean

   af.field1 = "filled in a"
   af.field2 = "public proc"

End Function

   filled in a   public proc
   filled in a   public BAS proc

Show quoteHide quote

Thanks everyone.  I ended up putting all of my UDTs in class modules to
prevent any more of these errors from popping up.  I'm just so used to using
OOP languages like C# that the seemingly un-classlike structure of VB6 kind
of threw me for a loop.

Chris

Show quoteHide quote

Un-classlike? I don't get it. The suggestion I made was to *replace* the
UDTs *with* classes... not move them *to* classes. Guaranteed not
un-classlike.

What ever works I guess.

I didn't move the UDTs to Class Modules, I just moved the variables to Class
Modules so I could use them like UDTs.  As for the un-classlike comment I mad
before, I just meant that there is no explicit statement in the code like:

class Add: noFunctionality {
    ....
}

to make me feel like I am actually programming a class, that's all.

Chris

Show quoteHide quote

Just wait until you have to use;  Set xxx = New <class>  every time you
want to create a new object full of variables.  Of course for frequent re-use,
you might want to institute a dynamic pool of such objects....  <g>

LFS

Using Set is now too much trouble? Sheesh. I'd rather type those 3 letters
everytime than have to put up with the reams of extra typing you have to do
in B#

If you want to discuss VB.Net, try:

microsoft.public.dotnet.genera­l
microsoft.public.dotnet.langua­ges.vb

The OP said he didn't feel like he was using objects.  I pointed out one
difference he'll need to keep in mind, over the UDT's he had been using.

Who mentioned anything about .Net???

LFS

VB.NET Discussion
Object navigation with <Enter> key stroke
Squeezing too much into a control...
Combobox, ITEMData and Reselected previous item
Use ActiveX DLL in VB.net
Rounding Negative Number Toward Zero
Dr. Watson "Access violoation" error
How to identify and extract bounced email info?
Auto Finding in ComboBox List
Wheel mouse and VB