April 4, 2008
Open your report form - option 8 on the form listing. you should be at
the top of your report - First page header. Above the line you will see
the codes listed that are to the right of your cursor. If those are the
codes you erred in, delete, right there. if not, right arrow until you
see the codes you want, then delete. Note that although there are
several items in the list, it is one printer code - it will all delete
at one point.
In case it has not been mentioned before, these should not just be typed
into the header, but added as printer codes. At the beginning of the
First page header, select ,ctrl-F7, 1, B
Don Codling
WP 12.0.0.602
Windows XP home, SP2
256 MBytes RAM
Charles G. Wolf wrote:
Okay, I made a mistake. How do I remove the existing codes to allow
new ones?
Don Codling wrote:
No. These codes go as the first codes at the top of our report. Their
sole purpose for practical concerns here is to tell WP that this is a
WP42 file.
The musical notes are part of your desired report, I believe. End of
Record? I'm not sure why you want that at the beginning, but in any
case, if you delete them, you lose it.
Don
Charles G. Wolf wrote:
Question: Do I delete the pair of musical notes when inserting the
codes?
Don Codling wrote:
FWIW, I've copied the relevant codes as a WP file in my computer
info directory, and when I'm making a new DP report for WP output
(or updating an old one, I just open that file and copy and paste
the codes into DP.
I have a shorter, simpler group, that works well - I forget why I
didn't like the longer string.
<236><0><0><236><130>
Very easy
Don
Brian Hancock wrote:
Hi Charles,
Once you insert those code in the top of the DP report it fixes
the problem you had and you do not need to make any changes in
WP. Initially I thought it would be a big deal because almost all
of my output at the time was producing WP merge files, but it
ended up being a very trivial problem with a simple workaround...
Bye
Brian
----- Original Message -----
*From:* Charles G. Wolf <mailto:[EMAIL PROTECTED]>
*To:* Dataperfect Users Discussion Group
<mailto:[email protected]>
*Sent:* Friday, April 04, 2008 11:00 AM
*Subject:* Re: [Dataperf] Merge record problem with 2.6
Hmm. Or, the merge code can be quickly inserted by WP. Too bad
it can't be fixed in DP.
Thanks, Brian.
Charles
Brian Hancock wrote:
Hi Charles,
Its is fortunately only a very minor annoyance... From
v2.6f
onwards header of WP mode file is not correct. As a workaround,
insert following Printer Control code (CtrlF7, 1, B) as very top
of a WordPerfect mode merge file
<206><0><0><206><192><00><255><0><255><192><14>
Regards
Brian
----- Original Message -----
*From:* Charles G. Wolf <mailto:[EMAIL PROTECTED]>
*To:* DataPerfect Users Discussion Group
<mailto:[email protected]>
*Sent:* Thursday, April 03, 2008 11:17 PM
*Subject:* [Dataperf] Merge record problem with 2.6
Hi Everybody,
I recently converted to DP 2.6 from 2.3c after being very
hesitant to do so. (I don't like to mess with success.)
I've come across what I will call a serious nuisance.
I rely on DP to produce "DP 4.2" merge reports, which is the
result of a secondary merge report in the "WP" disk file
mode. However, 2.6 does not produce this report
properly. Instead of a "NEXTRECORD" code showing up on
the first line
when opening the file in WP, a pair of musical notes show
up. However, the musical notes show in the first page
header
of the report definition screen in on both 2.3c and 2.6.
Somehow, this code that appears the same in both versions of
DP doesn't translate into the NEXTRECORD code when outputted
from 2.6.
Also, how does one find the version on 2.6 with the splash
screen gone?
Thanks.
Charlie
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
