Mike Cassano wrote:
Trying to replace FilePack with internal functions of the same name as the
ones in FilePack. The compiler is pucking on this because it thinks these
calls are still external, and I need way to get it to turn around and
realize these are internal functions.
I realized this using SanityCheck. Will Insider help here?
Mike
Is this what is causing 4D Compiler to crash? Or have you gotten to a
point where it just fails to compile?
Assuming Filepack is totally gone, i.e, not still in a 4DX folder, or as
mentioned before - not installed inside the structure - you need to
retokenize all methods that had the Filepack calls in them.
I've been told that compacting will do this for you but am not sure.
Beyond that you may just need to open each method that had a filepack
call and type CMD-Enter (or CTL-Enter on Windows) to retokenize the
method. The syntax highlighting should change to reflect a 4D method vs.
an plug-in call.
hth,
Brad
Thank you!
Mike
I tried all of that and it still crashes out. It did seem to get a little
further down the progress bar.
Any further advice? I'd like to use SanityCheck but my version doesn't
support 2003.6.
Again, it compiles on the Mac OS X, but not on the PC.
Mike
Christian,
Great ideas. I have done a lot of those types of things but I am
redoing
it. I have not done 'Clear compiled code' before so maybe that will
help.
I did manage to get it to compile in Mac X.
I will report back, thanks!
Mike
I have experienced the exact same thing last week, but for me the
only problem came on the Windows side. On the Mac I was able to
compile with no problems, when moving to Windows I received the same
error when Compiling during "Typing Directives". To be honest I'm not
sure what solution worked, but was finally able to compile on Windows
after trying several things. The db was moved from a Mac to Windows
via Transporter.
1. Before Transporting I cleared the compiled code.
2. Before compiling under Windows I ran Tools and fixed and compacted
the structure.
3. Reinstalled 4D
4. Removed the preferences for 4D and reinstalled my license.
It was some combination of those that allowed me to compile under
Windows.
On Jun 20, 2005, at 10:20 AM, Mike Cassano wrote:
Does it help to say that the compiler is on "Typing Directives"
when it
crashes?
Christian Cypert
[EMAIL PROTECTED]
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
- Douglas Adams
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
