Cyrus
Wed Feb 16 00:00:16 CST 2005
kd wrote:
> Thanks to all of you for responding to my query.
>
> I have now come to the understanding that, if I include files in <Project>
> <Project Info> [Files], then I don't have to provide an external copy of the
> same file, since it will be included in the .exe/.app. I can do this for .vcx
> files, since I do not want the customer to modify them. In the code, how
> would I tell the compiler where to look for the .vcx file unless I specify a
> path. My .vcx files are not in the default directory of the project.
>
> About the database and tables, my application involves inserting, updating
> and deletion of records. As far as my understanding goes, if I include the
> dbc with the tables in the project, then I would not be able to do the above
> mentioned operations. Or do you mean that the above operations can be
> performed and that only the dbc structure is read only.
>
> Thanks.
> kd
>
> "Cyrus Welch" wrote:
>
>
>>Tom Clark wrote:
>>
>>>Hi Kd,
>>>
>>>I think there has been a misunderstanding here, though I may be wrong
>>>because I do not have as much experience as others.
>>>
>>>Anyway, it is my understanding that you want to INCLUDE your VCX files,
>>>which is done by default anyway. Check <Project> <Project Info> [Files].
>>>
>>>When a file in INCLUDED that means all the information (code, data, etc.) is
>>>compiled into the executable, and since it is included in the executable,
>>>you do not have to deploy any included file -- it's already there. (I am
>>>not so sure about this but...) That means that you should not have to
>>>reference a path because the EXE should find the "included file" inside
>>>itself.
>>>
>>>I have never done it but if you did include the DBC and DBFs then you should
>>>be able to access those tables as read only tables like Wolfgang said.
>>>
>>>Regards,
>>>Tom Clark
>>>
>>>"kd" <kd@discussions.microsoft.com> wrote in message
>>>news:11EF0488-7921-4163-A4A5-E2963CB5F3A1@microsoft.com...
>>>
>>>
>>>>I just tried out what you said. Built an exe and then didn't include the
>>>>.vcx
>>>>in the deployed project. It works. The exe may be creating a reference I
>>>>guess. Thanks.
>>>>
>>>>Another question. My project involves updation of tables. That would mean
>>>>that I may have to include the tables in the deployed project. Would it be
>>>>possible to hide the database structure - I mean the relationship between
>>>>tables, primary and foreign keys, etc?
>>>>
>>>>kd
>>>>
>>>>"Eric den Doop" wrote:
>>>>
>>>>
>>>>
>>>>>If you include the VCX files in your project and you compile to APP/EXE,
>>>>>then you don't have to ship these with your APP/EXE. You can also include
>>>>>your tables in the APP/EXE, but then you won't be able to store new data
>>>>>in
>>>>>your tables.
>>>>>
>>>>>You can protect your application against the Refox decompiler by branding
>>>>>it
>>>>>with Refox, but this protection is not 100% safe.
>>>>>--
>>>>>Eric den Doop
>>>>>www.foxite.com - The Home Of The Visual FoxPro Experts - Powered By VFP8
>>>>>
>>>>>"kd" <kd@discussions.microsoft.com> wrote in message
>>>>>news:ED2E6879-59A5-40CD-8C4B-EF502FAE263C@microsoft.com...
>>>>>
>>>>>
>>>>>>Hi All,
>>>>>>
>>>>>>I need to deploy a foxpro application. The tables are foxpro tables and
>>>>>>the
>>>>>>project also has .vcx files. How to package the tables and the class
>>>>>>libraries so that, when the application is deployed, the tables class
>>>>>>library
>>>>>>files are hidden, even if the customer install visual foxpro
>>>>>>developer's
>>>>>>kit?
>>
>>I include read-only tables inside my EXEs all the time. If the customer
>>is never supposed to change them, and it's only supposed to be a
>>developer that changes them, this sure adds another layer of protection.
>> A lot of my functionality is table driven, but requires objects and
>>such that I had to create, so the definition files are all included in
>>the EXE so I don't have to worry about users deleting them or something
>>stupid like that.
It doesn't matter what the path is that you put in because the compiler
will handle all that at compile time and will store the paths to all the
files. Once the app is compiled it won't matter where they are because
it will also see what's in the app/exe no matter where you tell it to
look for them.
--
Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com