Recent content by grahamrhind

Thanks Ben. No driver or service is installed for that cloaking - it just translates one character with another and writes it back to the field. Stumped indeed!

@BigBadBen Some good thinking there! Thanks! Renaming dbf->txt and copying the txt does NOT result in the corruption. Renaming that txt->dbf in the destination directory also does NOT result in the corruption. So something is affecting files only with the .dbf extension. Foxpro is the...

Hi Olaf, Some fair comments, but to emphasize some points which may have become lost in the length of this discussion: 1) The directory concerned is \program files (x86)\ and not \program files\ 2) Important to note is that "untouched" standard dbf files can be copied to that directory...

@dilettante: thanks, though I only understood about 3 words in your message. If data (as lookup tables) is being shipped with an exe program, I would have though that that directory was the place it should go. Installing the whole program outside the \program files (x86)\ directory doesn't...

Olaf, Changing the permissions in InstallShield does not change the issue. I.e., even with "Full Control" the dbf file contents still become "corrupted". I'm going to call it a day on this issue - it's taking too much time and effort, and I have a workaround - not installing to that...

Hi Olaf, Yes, I'm using InstallShield Express Limited Edition for Foxpro 5.0. I've found a way of setting the permissions in that version on this machine, so I'll give that a try. Graham

Hi Olaf, You said: "To me the second version simply looks like a double encrypted version" Yes, I agree. And I know that a simple copy shouldn't do that to a file. But that's what is being done. That's the mystery. I can copy the files to other places on the disk, to other directories...

Thanks Linney. The drive is checked for errors every week, and a chkdsk shows no problems. This issue has been around for many months, so I think it's an OS issue that I can't fathom. The dbf files are "encrypted" but only by substituting one ASCII character with another, so the files' fields...

Possibly a weird issue that I'd like to understand ... I discovered that the contents of my dbf files (created by Visual Foxpro 9) were becoming "corrupted" when installed in the \program files (x86)\ directory of a Windows 7 64-bit system, whilst installing them anywhere else on the disk, or...

Hi Olaf, I appreciate the time and effort you put into answering my, and other, queries - I really do. But I'm not sure you're quite getting this issue. Or I'm missing your point entirely. Because: 1) You say: "Your dbfs just look to me like the unencrypted versions you install" Please look...

Hi Olaf, This has nothing to do with VFP, actually, and no decryption takes place. The corruption occurs when moving a dbf into the'\program files (x64)\ directory on a Windows 7 64 bit machine. Even doing it via Windows Explorer it causes the same corruption, so it's clearly something to do...

Going back to my initial problem, I have found out that tables with strings processed using chrtran have the same problem - that they become corrupted during install. (See: http://dl.dropbox.com/u/450542/BeforeAfter.png). Following this through each phase in the process I have found that it...

I think it may just be down to a simple case of having reversed the parameters at some point in the process. I'm just having a dizzy time today. Thanks for the extra information, though.

Mea culpa, and silly me. Thanks Olaf. I'll have to dig deeper as to why I'm getting other weird results back ....

Some further information about using CHRTRAN() to encrypt. I found out (too late ...) that double letters within words are not both transformed so that the "unencrypted" version is no longer correct. Thus, for example...