Problems with user defined types (VB3)

I have a big problem with the VB3 editor, concerning type declarations!!! If I start a program while debugging code, the following mysterious thing happens:
After editing a line with an user-defined-type and continuing the program, VB3 does not accept the user-defined type (udt) anymore (error message:"Identifier is not an object or user-defined-type"). When the program is stopped and you want to start the program again, the same error message comes up.
Finally, if you redefines the variable, a simply space in the line of ("Global gtVar as tType"), and starting the program again, everything works without problems until you edit a line with this udt.

Some additional informations:
This bug has not appeared from the beginning in the program. Not every global udt has this bug. The size of the udt is not responsible for the bug. Small types and big types have the same problem.

To restart VB can´t be the solution!!!
farenetAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MsoftCommented:
Hi,
I think that all UDT must be global and declared In Module.
Maybe you declared variable and UTD at same name or same name to VB Global Constants.



0
coqCommented:
Do you have decleared it public?

/johan

0
bhowardCommented:
I have seen this behavior with VB3 on several occaisions.  I write it off to the general flakiness of the product, save my files, exit VB, and reload VB.  In fact, this is my response to any number of flaky behaviors VB3 has.
0
farenetAuthor Commented:
Edited text of question
0
mheacockCommented:
Restart VB.  It is simply a bug in VB 3.  There is probably
a specific way to always recreate the error within any
program using UDTs, but so far I haven't figured it out.
Just something weird in VB3 that you'll have to live with.

Save, restart.  It's the only way.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.