On 2016-12-03 04:36, Wollenhaupt, Christof wrote:
Can you elaborate on that? Is that because of the binary storing in
VCX
files? Would that also apply to SCX files too?
long version: http://foxpert.com/docs/security.en.htm
*TL;DR:*
SCX files are a bit more difficult, but not by much. The approach is
the
same.
SCX and VCX are opened in the system data session when you execute
them.
Code injection allows you to copy those files out of the running
application.
Code in the OBJCODE is never encrypted. Clearly visible when you look
at
the help file for the COMPILE command and the ENCRYPT option.
The report designer is always the easiest. If you let the user modify
reports try this in your EXE: Open the report designer, right click to
open
the data environment, right click to add a file. Pick Other. In the
file
open dialog enter the name of a VCX or SCX file that is embedded in the
EXE. The name must be in quotes. You will see the file being available
in
the report data environment.
WOW! Glad I use PRG classes!
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
