Thank You! to all who responded to my post below regarding converting an old
FBII ap to FB3 and some strange compile time errors.  Alain was the closest.
The problem ended up being the pict.fltr included in my PG project.  Once it
was removed the ap compiled fine and now I almost have it fully running.
The ODD thing is, the pict filter included was the current version 4 filter
(at least thats it says in the filter source).  I did a search and removed
all the old versions so I'm pretty sure it's not picking up a bad one. Can
some one check and see if the version 4 pict.fltr is indeed working?
Thanks to all of you for your help.  This is a great community.
Tony

----------
>From: "aeblack" <aeblack@...>
>To: futurebasic@...
>Subject: [FB] Soooooo close... I think
>Date: Sat, Feb 10, 2001, 4:38 PM
>

> I've been working on converting an old FBII project to FB3 and have gotten
> very close (literally down to the last error message) before getting
> hopelessly stuck.
> After fixing the very last error generated when compiling with the FBII
> runtime I suddenly get 4 brand new errors that I can find no reference to.
> They are:
> DISPOSEBWORLD unresolved
> MYDISPOSEBWORLD unresolved
> BUILDBWORLD unresolved
> QD32SUPPORT unresolved
> When I try to view the error the following dialog appears:
>
> This error was in the project file's data fork and may not be viewed with
> the FutureBasic editor.  The pseudo-code that generated the error was
> created by this error, then sent to the compiler.
>
> Help!  I have no idea what created these errors or how to correct them.
>
> Thanks.
> Tony
>
> --
> To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>