Marc G

Thanks. Your script works nicely on the first page of my report. I use a title header on the first page. Once page one, however, I get the correct page number but gPages comes up blank. I added a dialogue box to the script for testing purposes and it reports the correct value for gPages. In browse mode, gPages also shows the correct value. In preview mode, though, it comes up blank -- except in the title header on page 1.

Instead of just listing the current page number in the header of a report, I need to list page 1 out of X where X is the total number of pages in the report. I could not find a function to calculate total pages in report. Is there such a function. Or does someone have a good formula or work-around for this. My client sends our multi-page proposals and wants to be sure the recipient knows when pages are missing. Thanks Version: v6.x Platform: Windows 2000

Is there a problem with using the "auto-enter from previous record" option on a field in a portal? I have created a db where this option works fine. As the user creates a new record, the vendor field is automatically populated with the vendor from the previous record. However, when I use this db as a child table in a portal, the auto-enter behaves unpredictably. As the user creates a new child record, it populates the field with info from an existing record, but not always the immediate previous record. This produces unpredictable and frustrating results. Is there a sort issue involved (I tried different sort orders as part of defining the relationship between the parent and child db)? Or is it just not possible to use this field option for a portal row?

I need to create duplicate records of both a parent record and related child records. The parent dB is "proposals" and the child dB is "line items" for the proposals. My salesmen want to be able to create a duplicate proposal with all the line items and then modify the line items to create an alternate proposal for the customer. How can an automate the process so at one click they can: 1. create a duplicate of the parent records (with a new proposal# auto indexed) 2. Create a duplicate set of all the related line items with the duplicates assigned the new proposal number. I've tried a few approaches, but have hit a roadblock on every approach. Any help is appreciated. Thanks