Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How to avoid compilation errors using SP in a program?
Message
 
General information
Forum:
Visual FoxPro
Category:
Project manager
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01151299
Message ID:
01151594
Views:
31
Naomi,

There's a difference between a compile error and the project unable to find all the components that you've told it that are supposed to be there.

FWIW I don't see the exe size change by a single byte, with this main.prg:
external procedure sp1

open database testsp
set database to testsp

return sp1()

* this is sp1:
procedure sp1
return 1
between when the database is in the project and excluded and when the database has been removed from the project. When it's removed a build gripes, as well it should, in order to make sure that the exe isn't going to fail at runtime. Of course it can still fail if the code doesn't OPEN and SET DATABASE to make the SP available.

But the exe is 24,332 bytes in size with or without the database in the project.

>It's not enough, David.
df (was a 10 time MVP)

df FoxPro website
FoxPro Wiki site online, editable knowledgebase
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform