?
Solved

Problems with user defined types (VB3)

Posted on 1997-04-10
5
Medium Priority
?
206 Views
Last Modified: 2008-03-06
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!!!
0
Comment
Question by:farenet
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 

Expert Comment

by:Msoft
ID: 1425193
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
 

Expert Comment

by:coq
ID: 1425194
Do you have decleared it public?

/johan

0
 
LVL 1

Expert Comment

by:bhoward
ID: 1425195
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
 

Author Comment

by:farenet
ID: 1425196
Edited text of question
0
 
LVL 3

Accepted Solution

by:
mheacock earned 200 total points
ID: 1425197
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

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Most everyone who has done any programming in VB6 knows that you can do something in code like Debug.Print MyVar and that when the program runs from the IDE, the value of MyVar will be displayed in the Immediate Window. Less well known is Debug.Asse…
This article describes how to use a set of graphical playing cards to create a Draw Poker game in Excel or VB6.
Get people started with the process of using Access VBA to control Outlook using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Microsoft Outlook. Using automation, an Access applic…
Get people started with the process of using Access VBA to control Excel using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Excel. Using automation, an Access application can laun…
Suggested Courses
Course of the Month11 days, 7 hours left to enroll

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question