ralph
12/29/2011 7:05:00 AM
On Wed, 28 Dec 2011 20:55:32 -0800, BeeJ <nospam@spamnot.com> wrote:
>I asked about this before and got no viable answer.
>So I will ask again since maybe someone has percolated on it and has
>some suggestions.
>
>I want to create a VB6 app that contains / retains editable text.
>So when I pass the app, the embedded data goes along inside.
>
>I suggested using propertybag but was told that would not work.
>Suggestions please.
>
>What am I trying to use it for? An app that stores encrypted passwords
>etc. that I can add, edit etc. I want one file, the app, so I do not
>have to maintian multiple files/formats etc.
>
Another non-viable answer follows:
If this is something inhouse or recreational sharing you can use ...
1) the .DATA section.
2) the Resource file mechanism.
3) Simply append a file to the end of the executable.
4) Alternative File Stream
However, none of these schemes will work in a 'normal' Windows
environment without User help. You'll have to turn off Virus Checkers,
store the App in a non-Apps folder (eg. \appdata), and a zillion other
little annoyances and gotchas. (Well maybe only a couple of dozen.)
If you are trying to protect the information from anyone that has
physical access to the file - give it up. All schemes are sure to
fail.
Besides, you should NEVER store single passwords. If this is a
distributed application investigate using a Public Key.