Have to Break Compatibility every time???

I just compiled a DLL project in VB6, set the project to binary compat. (to the dll I just compiled) and closed the project.

Re-opened, made NO CHANGES whatsoever and it says I have to break compatibility because it can't find a property that IS THERE.

I've been going around in circles like this for HOURS.  What gives??

Wayne
Tuesday, February 10, 2004

What am I missing here?  This is the message I get:

Original definition:
Property Get Flag(eFlag As DCAgentLib.ClientStateEnum) As Boolean

Current definition:
Property Get Flag(eFlag As DCAgentLib.ClientStateEnum) As Boolean

Wayne
Tuesday, February 10, 2004

I did not add any enum values.

Wayne
Tuesday, February 10, 2004

Is DCAgentLib.ClientStateEnum public?

Philo

Philo
Tuesday, February 10, 2004

I was about to cry like a little girl, so I brought a fresh mind in to look at it.

The problem was that I had a property that had a Public Get procedure and a Private Let procedure (which worked fine for development, but when release day comes...of course it doesn't work :)

Sorry for freaking out, but I was battling with this for about 2-3 hours.

Wayne
Tuesday, February 10, 2004

It's happened to all of us!

Almost Anonymous
Tuesday, February 10, 2004

Congratulations, you just gained experience. Your aptitude has not changed. [grin]

(referring to another thread)

Philo

Philo
Tuesday, February 10, 2004

2 Days ago I moved a class location in the hierarchy but was interupted before I deleted the previous reference.

Spent at least 2 hours trying to figure out why it didn't exist, or did.

I wept openly!

Tuesday, February 10, 2004

I once spent about 8 hour debugging a paradox database. 

I had used a reserved keyword as a field name.


That was back in 1992 or so, long before I became a programmer. But that story is next to the the phrase "Down a rat hole" in the dictionary.

The real Entrepreneur
Tuesday, February 10, 2004

Nobody rants against VB better than the author of Hardcore Visual Basic:

http://brucem.mystarband.net/mckinney1.htm

Tuesday, February 10, 2004

At least it sounds like you understand compatibility. I worked on an application once that contained on the order of 25-40 DLLs and ActiveXEXEs. And they (existing project team) *weren't* using binary compatibility. I tried and tried to explain that it needn't take 2 days to build a VB project. And that using compatibility would be painful one time (getting the source code control straightened out), as opposed to painful every single day.

But ultimately, like any good American (sorry USAian), I gave up and got the hell out of there...

Rob VH
Wednesday, February 11, 2004

If using VB6 - Set Project properties to Project Compatibility in the Component tab of the Properties dialog box.

KS
Wednesday, February 11, 2004

  Recent Topics

  Fog Creek Home