>
>////////////////////////////////
>Ed
>
>Ahh, maybe I should rethink my approach- The business requirement is that first of all, these are control documents. Not just anyone can access them. Even among those who can, changes are NOT allowed - they can't even print them. They can look at them on screen - that's it. Currently I use network security, but that does not disallow the choice of opening a file with read only access to a drive, changing it and saving it to another location on the network where the user has full access. We can't have that with these kinds of documents. They are proprietary (design instruments) and we also don't want to run the risk of someone "selling" them to a competitor. We also can't have someone making unauthorized changes. So I figured I had the most control over them from within VFP if I treated tham as embedded objects. If one is printed I need to log date time and who printed it. If it's changed I need to log that as well. If I link them (by way of general field or just a text field pointer to
>their directory/name) that still means someone could open from outside of VFP and circumvent required security. The binary data in a memo might be OK, but I've had far too many memo file corruptions to feel that's a safe bet. Any suggestions?
>
>Susan
>/////////////////////

I wonder if this is possible with in place editing.