I need to make secure (ie prevent tampering) the data for a large 16-bit legacy application running under Windows NT4. My thought is that I use Windows security to hold the data with access limited to a single user account. I then wrap my legacy app in some VB code that uses LogonUser and CreateProcessAsUser to fire it under the special account. That way, my users only have access to the data through the app.
I would welcome any advice or anticipated pitfalls. (I also might need to do this on Citrix under NT4 or 2000. Any problems?).
I would welcome any advice or anticipated pitfalls. (I also might need to do this on Citrix under NT4 or 2000. Any problems?).