4.0.2 db in 5.5, expandable TESOs don't expand, Print This Record tool bar item prints all records

[Steve Kane]

On Mar 16, 2008, at 10:49 AM, Gary Yonaites wrote:

>
> On Mar 15, 2008, at 6:26 AM, Steve Kane wrote:
>
>> Hmmm. It looks like every form is corrupted. This is turning out to
>> be far more tedious than I had thought. There does not seem to be a
>> way of automating it. I can use GraphicsMode in a procedure but can't
>> do anything else after that. Is there a way to automate this?
>
> I found this to be a rather fun challenge. I worked out a method that
> will walk through and copy all items from every form onto a new form
> one at a time until every form is duplicated. You will need to enter
> a new form name for each form as it is created and duplicated and
> then you will have to go through and delete the old forms and rename
> your newly created forms back to what the original names were. The
> method requires two new procedures that I have named DupForms/8 and
> DupForms/9. The only import part of the name is the /8 and /9
> endings. Here is the code for each of the procedures:

As the kids today say, "OMG". That's amazing. I can't wait to try it.

I am thinking seriously of rebuilding and redesigning the Phone Book  
file from PowerTeam. I've been using it constantly since I bought it  
maybe 15 years ago. I want to leave behind all the resource file  
stuff. To do this in a way that minimizes carrying over any  
corruption that has crept into the file I was thinking that the best  
way would be to copy all the procedures into a new file and then copy  
all the forms in the way you describe above (ie selecting, copying  
and pasting all the objects rather than doing a CopyForm/Pasteform),  
except into the new file rather than within the original file.

Do you happen to have written a procedure that can copy all the  
procedures from one file into another file?
Can the DupForms procedures be modified to copy all the forms into a  
new file rather than into the same file?