Getting the ball rolling. Which VB6 projects are you working on?

[SomeYguy]

.....UDTs in VB6 are such utter garbage.....

I'm using UDTs in a few of my programs from over the years with no ill effects.....Should I not be using them?

[Niya]

I'm using UDTs in a few of my programs from over the years with no ill effects.....Should I not be using them?

Ok let me clarify before I end up doing some damage here.

I don't think anyone should stop using UDTs. Use them as much as you like. I'm saying that I have a problem with them. UDTs have so many rules, restrictions and oddities that unless you're actively using VB6 on a daily basis, UDTs are going to be a constant source of frustration.

I've been programming mainly in VB.Net for several years. Stuctures and Classes in .Net don't have all these restrictions and oddities. They are extremely straightforward to use and their behaviors are clearly defined and quite consistent. You're free to use them however you like. They are treated as first class citizens in .Net(basically like any primitive type such as Integers) which simplifies a lot of things.

I'm way too used how freely .Net handles structured data and I really don't want to re-train myself on all the idiosyncrasies of UDTs in VB6 so I elected to avoid them entirely before they drive me insane. But if you understand all the rules, pitfalls and traps, I'd say use them to your heart's delight.

[SomeYguy]

Ok let me clarify before I end up doing some damage here.

I don't think anyone should stop using UDTs. Use them as much as you like. I'm saying that I have a problem with them. UDTs have so many rules, restrictions and oddities that unless you're actively using VB6 on a daily basis, UDTs are going to be a constant source of frustration.

I've been programming mainly in VB.Net for several years. Stuctures and Classes in .Net don't have all these restrictions and oddities. They are extremely straightforward to use and their behaviors are clearly defined and quite consistent. You're free to use them however you like. They are treated as first class citizens in .Net(basically like any primitive type such as Integers) which simplifies a lot of things.

I really don't want to re-train myself on all the idiosyncrasies of UDTs in VB6 so I simply elected not to use them entirely before they drive me insane. But if you understand all the rules, pitfalls and traps, I'd say use them to your heart's delight.

Roger that and understood. I just wanted to make sure that there isn't a massively better way and that my software won't bomb during the next planet alignment on the 4th Sunday at the full moon or something .....

[Niya]

Roger that and understood. I just wanted to make sure that there isn't a massively better way and that my software won't bomb during the next planet alignment on the 4th Sunday at the full moon or something .....

Oh yes sure. You're perfectly fine.

This thing with UDTs is more of a me problem than anything else. To use an analogy, using UDTs makes me feel like a formerly rich person trying to get used to being poor again. So your programs are not going to break. Don't worry.