Hi all,

I am still on OI 9.4, but soon to fiinish the install of OI 10.2.

I wanted to edit/create a Form, so accessed the AREV Main Menus: Define, Report, Form. I get an error stating that PAINTFORM is an unrecognized word.

Where did this go? What do I use instead? I've hunted around, but unable to find alternative.

Robert.

Hi all,

I am still on OI 9.4, but soon to fiinish the install of OI 10.2.

I wanted to edit/create a Form, so accessed the AREV Main Menus: Define, Report, Form. I get an error stating that PAINTFORM is an unrecognized word.

Where did this go? What do I use instead? I've hunted around, but unable to find alternative.

Robert.

[F5] PAINT

Hi Barry,

To be clear, this is a Form that should be saved in the REPORTS file, with 1st part of key being "FORM*" and 2nd part being the nominated name of the Form.

I tried your suggestion, and looked for something in the Menu items to indicate that this is NOT to be a data entry window, but rather, a Form. Didn't find anything.

I seem to recall (in years gone by), that when painting a Form, that the "paint" Menu was different (options, etc.) to the regular Paint Menu.

Maybe I should be looking for a PAINTFORM Menu??

Robert.

Hi Barry,

To be clear, this is a Form that should be saved in the REPORTS file, with 1st part of key being "FORM*" and 2nd part being the nominated name of the Form.

I tried your suggestion, and looked for something in the Menu items to indicate that this is NOT to be a data entry window, but rather, a Form. Didn't find anything.

I seem to recall (in years gone by), that when painting a Form, that the "paint" Menu was different (options, etc.) to the regular Paint Menu.

Maybe I should be looking for a PAINTFORM Menu??

Robert.

PAINTFORM works for me

I see it in VOC

<1>RBASIC

<3>SYSOBJ

<4>PAINT

Hi Barry,

Well, that would certainly help if I had this record in my VOC. Don't know what happened there. Thanks for that.

When I edit a Form record in REPORTS, I see it looks very much like a Data Entry window defn. The "prompt count" is in field 16, with the prompts following. Does that sound right?

Robert.

Hi Barry,

Well, that would certainly help if I had this record in my VOC. Don't know what happened there. Thanks for that.

When I edit a Form record in REPORTS, I see it looks very much like a Data Entry window defn. The "prompt count" is in field 16, with the prompts following. Does that sound right?

Robert.

Sorry, dont know anything about REPORTS.

Did you copy your Arev VOC to the AREV_DIR VOC (No overwrite)

You could have a file VOCAPP that points to your AREV voc already that you can copy from. Not saying that you should have it, but I dont remember creating the alias (assumed), but I did have to do a lot of fiddling to get everything to gel!

Hi Barry,

Well, that would certainly help if I had this record in my VOC. Don't know what happened there. Thanks for that.

When I edit a Form record in REPORTS, I see it looks very much like a Data Entry window defn. The "prompt count" is in field 16, with the prompts following. Does that sound right?

Robert.

You do know there is no actual difference between a "window" and a "form" in ARev, right? The only difference is that a "form", when stored in REPORTS, is pushed down 15 fields to handle some house-keeping used for other, non-FORM, report types.

What are you attempting to accomplish?

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

Hi Aaron,

I have since learned that the record structures are the same.

I am looking at an old application, and I have written a utility program that changes field names used in windows, reports, merges, labels and forms, converting "." to "_".

Robert.

Hi Barry,

In AREV32, the REPORTS file now have ALL types of reports contained within. The keys to the records are prefixed by their Type: RLIST*, MERGE*, LABEL*, FORM*, FILTER*, and perhaps QBE*.

As for the VOC issue, after you gave the VOC defn for PAINTFORM, I checked in another application, and there it was! Don't know what happened to the defn in the other application.

Thanks again,

Robert.

Just to be clear AREV32 is === AREV 3.12. The code base has not changed and it is not viewed as an actively developed product. It's still the same baby Aaron birthed out of the Rev labs 29 years ago!

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

Hi Andrew,

It's scary when you see the number of years passed WRITTEN DOWN!

I consider myself extremely fortunate to have been introduced to my beloved AREV s/ware back in 1989/90 in Sydney Australia. It just ticks all the boxes!

Just on the reply from Aaron saying that PAINT and PAINTFORM are identical, that appears to be true functionally, but the resulting records written to the Template file vs REPORTS "FORM" are different. All records in the Template files when using PAINT have the prompt count on <1> followed by the prompt details, whereas PAINTFORM puts this count on <16> and followed by the prompts. I discovered this when I wrote my utility prog to go through the various "painted" screens and report files to change field names containing "." to "_", in all their locations, including Catalyst "B/C/E/X" calls. I also noted with interest that "P" calls did not need to have field names updated. I assume POPUP does a quick convert when it fails to read a field name from the Dictionary. Clever.

Cheers,

Robert.

Hi Andrew,

It's scary when you see the number of years passed WRITTEN DOWN!

I consider myself extremely fortunate to have been introduced to my beloved AREV s/ware back in 1989/90 in Sydney Australia. It just ticks all the boxes!

Just on the reply from Aaron saying that PAINT and PAINTFORM are identical, that appears to be true functionally, but the resulting records written to the Template file vs REPORTS "FORM" are different. All records in the Template files when using PAINT have the prompt count on <1> followed by the prompt details, whereas PAINTFORM puts this count on <16> and followed by the prompts. I discovered this when I wrote my utility prog to go through the various "painted" screens and report files to change field names containing "." to "_", in all their locations, including Catalyst "B/C/E/X" calls. I also noted with interest that "P" calls did not need to have field names updated. I assume POPUP does a quick convert when it fails to read a field name from the Dictionary. Clever.

Cheers,

Robert.

I never said they were identical. I said:

The only difference is that a "form", when stored in REPORTS, is pushed down 15 fields to handle some house-keeping used for other, non-FORM, report types.

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

Aaron,

Oops, sorry. Clarification acknowledged.

Robert.

View this thread on the Works forum...