>>Just a thought - if all the .scx, .vcx and .frx files are included into an app, are we sure they don't need packing? I mean, they're all .dbf in essence, and have lots of memos. Pjx files have this option in the project manager, but is anyone sure this packs all the .dbf style .??x files. This could significantly reduce the apps' size, if I'm right.
>
>I'm pretty sure the .vcx need packing, they don't seem to be handled the same way as other object tables by the project. I think the scx & frx are packed with the project (just guessing, because when I open them they rarely have any deleted records even after a long time)...

Actually, I meant packing the memos. Remember Garry's diet - if it works on .dbcs, why not the other stuff. I tried a bit today, but didn't change a byte. I was probably wrong - seems to be .scx and .frx get copied into arrays or cursors during editing, and copied back when saving. You can notice in a .frx that the ordering of objects on the layout maps 1-1 to physical positions of the corresponding records in the .frx; once you change their order, the record physically goes there. Nobody would do that by manipulating records in a table, but with an array, why not. Then you sort the array and copy it back into the table. If I'm right (this time), then these files are as thin as they can be. Seems to be only the .vcx'es need some packing (VCX editor takes care of that).