Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Hiding VFP Engine
Message
From
29/11/1999 22:54:15
 
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00296556
Message ID:
00296693
Views:
23
>>I don't think its necessary either. But I can see for a shrinkwrapped application where the authors might not want to reveal any of these details.
>
>Why? Does the app become more salable written in VB, (something that might cause some to blush and stammer in and of itself) or Delphi, or VC++?
>

No, the app might look more professional if it doesn't reveal any details, VFP, VB, DElphi, PB, or whatever.

>The odds are that somewhere, if someone really wants to know your lineage, they can figure it out...

This is easy enough- with any of the VS products, just look to see what runtime files install. Even with an independent exe, I'm sure that every tool leaves some sort of traceable footprint inside the file...
But I'm not talking about someone who wishes to investigate, I mean the user who doesn't know and doesn't care. Why associate the product with the tool used to build the product? When I install and use TurboTax, the software doesn't bother to inform me that it was written in TurboPowerDevBuilder 2000 (or whatever).
Erik Moore
Clientelligence
Previous
Reply
Map
View

Click here to load this message in the networking platform