Compile problem

[Guest]

I have not used PB for while, (2 month) and now, when I try to compile program, which I have compiled in past over 700 times, I get message stating "Cannot compile Basic file XXXX" "Incorrect Function". I have totaly erazed and cleared registry and than reinstalled PB several times and still the same message.
It will not compile any program including those provided by PB as samples.

Does anybody have an idea. Please Help.
Thank you

[José Roca]

You should provide more information, such the error number and the contents of the line of code where the error happens.

[Scott Slater]

Anti-Virus issue?

[Guest]

Thank you Scott and Jose
That is the only message that comes up, NO Error Number , No Line bumber
Jess

[Steve Rossell]

What compiler and version are you using? I could not locate a registration for any products under your name?

Sounds like you are using an old version of PBWin. Try placing your source code in a shorter directory path (such as c:\test) and see if you can then compile. Also make sure that all paths in your rc file are correct.

[Jim Padgett]

Safe MOde

Does it do the same in safe mode?

[Fred Buffington]

Check your function name for anything else with the same name (though the more likely message in this case would be a duplicate error message).

Another posibility is wrong name for a function that is in a dll and trying to call it from another program. (though not found error should be shown)

[Michael Mattias]

Older versions of compiler did that 'sometimes' when there were relative (?) paths in the #COMPILE statement. (Not all the time, and the specific conditions I can't recall).

Or maybe if was if the #INCLUDE path was too long, making the total command line (when IDE launches compiler) too long?

I'm sure the word "path" was part of this issue but in precisely what context I just cannot recall.

MCM

[Fred Buffington]

I had it happen yesterday and I think the culprit was a misnamed resource file
(using version 6.11) - I had renamed a group of programs and include and pbr files but failed to make one or more changes in the source code. But it was easilu and quickly found.

[Cliff Nichols]

Last time it happened to me, either my exe was buried too many levels deep (or the length of the path was too long) or the resource that was being used was buried that deep or that long.

[Michael Mattias]

>(using version 6.11)

Not to be a shill or anything, but I believe there might be an upgrade available.....

Not that 6.11 is not very nice... it is, however, very nice only relative to 6.0.

It's not too soon to start dropping hints to Santa.....

[Cliff Nichols]

>(using version 6.11)

I missed that, but being an advent of "Sometimes Older is better" I am not surprised

That said...it is "TOTALLY" worth upgrading cause 9.0 caused one heck of a spur, and 9.01 was a total boost and from what I hear 9.02 (future release) will make you wonder WHYYYYyyyy the heck you stuck with the version you have, when other versions could so simply fix a problem where you got stuck.
(this coming from a guy that recently had to revisit VB cause it was the only common language, and the more I work with it, the more I find myself muttering..."Why do I have to jump these hoops? PB I could do this in X number of lines.....GRRRRRrrr"...."Oops here we go again...1 line in PB would fix all the garbarge hoops I need here"....."Oooops here we go again...another one....")

Not that I am picking on VB (although now that I know better it deserves it )

A jump from PB6 to PB9 I am 100% you will LOVE!!!! (especially the 'lil' things that have probably annoyed you for years)