Upgraded from Arev 2.12 and there are a few weird things happening -

1. On most workstations, when we try to do a Select or List on an indexed field, it always comes up with a

1. – meta compliation error –

                  and then

1. – error in Reduce 0 —–

and will not run. Remove the index on the field and everything works fine. Put it back on and get the errors again. This is on every table/file. Now, if I run it from my workstation (new workstation) - it runs fine with or without indexing on a field.

2. After upgrade, when going to the command level and typeing in

       CW MAKERLIST

 and specifying either the REPORTS or QUERIES table and doing an

 F2 at the Template Name prompt, it shows "Empty" for the report

 list when there are over 1670 reports in the table.  If we try to

 go to the APPMAIN menu and do Define/Report/Easywriter and pull

 from the Library, it always breaks with variable exceeds maximum

 length (expanded memory enabled with proper settings), so the users

 cannot get to the reports area to modify or create new reports.

3. When in a window and going to a text field, lets say a user has

 copied information into the buffer and pastes this information into

 the text field (after doing an F3 to "zoom" the text field up, then

 they do a Ctrl-Z to reformat the text, the system asks if they want

 to reformat the text to fit the area, we say yes, but all it does

 is to put in a blank line, and does not reformat the text!!!

4. This annoying message (W364) when exiting a window about

 "This window contains unsaved changes, Are you sure you want to 

  exit now", and the default is "No" (as if AREV users are not

  experienced or are stupid people). - Is there any way to get rid

  of this message/confirmation?

Thanks in advance for any help/suggestions you'all can provide!!!

Most of these seem like 3.10 errors that were fixed with the 3.12 update.

The new message is the default for all the 3.12 code. You can shell the message and replace the default with a Yes so hitting Esc twice kills the window.

Here's program I wrote a real long time ago….

0001 SUBROUTINE DOUBLE_ESCAPE

0002 /*

0003

0004 This program is proprietary and is not to be used by

0005 or disclosed to others, nor is it to be copied without

0006 written permission from Revelation Technologies, Inc.

0007

0008 ÷ VERSION : AdvRev 3.11

0009

0010 ÷ PURPOSE : To duplicate as best as possible the double escape from old

0011 versions

0012

0013 ÷ AUTHOR : Revelation Technologies Technical Support

0014

0015 ÷ CREATED : 06-08-94

0016

0017 ÷ PROCEDURES :

0018

0019 ÷ WARNINGS :

0020

0021 ÷ THEORY OF OPERATION :

0022 This program is used to change the default behavior of the system message

0023 W364 (The window has changes….).

0024 To dplicate this functionality with any other system message, follow these

0025 simple instructions:

0026 1. Create a new record in the MESSAGES file with the same key as the record

0027 in SYSMESSAGES you want to change the default

0028 2. Enter a C in line 1. (C is the cataylst type message)

0029 3. Enter a valid catalyst code and command sequence in field 11 (seperate

0030 the code and command by a value mark.

0031

0032 How and why this works:

0033

0034 The system defaults to checking the MESSAGES file before checking the

0035 SYSMESSAGES file. By placing a record in the MESSAGES gfile you can

0036 override the default behavoir of any system message. In this case, we are

0037 replacing the system message with a message of C type. A C type message

0038 does not display a message at all, but instead executes the catalyst

0039 code and command statement that is found in field 11 (MAPSCRIPT$)

0040

0041 Our program will read in the original message, pass a default value of YES$

0042 to the message. When the subroutine is over, it must pass back the value

0043 MSG expect to see in the return value list as @ANS. (The returned value

0044 list is the third parameter of message)

0045

0046 ÷ REVISION HISTORY (Most CURRENT first) :

0047

0048 DATE IMPLEMENTOR FUNCTION

0049 ——– ———– ——–

0050 MM-DD-YY initials Modification

0051

0052 */

0053

0054 *÷ COMMON Variables (Terminate with '%') :

0055

0056 *÷ LABELED COMMON Variables (Terminate with '@') :

0057

0058 *÷ EQUATE Variables (Terminate with '$') :

0059

0060 EQU RTI$ TO 'Copyright (C) 1990, Revelation Technologies, Inc.'

0061 EQU TRUE$ TO 1

0062 EQU FALSE$ TO 0

0063 EQU YES$ TO 1

0064 EQU NO$ TO 0

0065 EQU OTHERWISE$ TO 1

0066 EQU NULL$ TO ""

0067 EQU SPACE$ TO \20\

0068

0069 *÷ MESSAGES called (Terminate with '$') :

0070

0071 *÷ DECLARED - FUNCTIONS called :

0072

0073 *÷ DECLARED - SUBROUTINES called :

0074 declare subroutine msg, fsmsg

0075 /*

0076 ÷ INDIRECT - FUNCTIONS/SUBROUTINES called if known (Make COMMENTS) :

0077 */

0078

0079

0080 *÷÷ PROGRAM TOP

0081

0082 open 'SYSMESSAGES' TO sysMessages else fsmsg(); return

0083

0084 read map from sysMessages, 'W364' else fsmsg() ; return

0085

0086 retVal=YES$

0087 msg(, map, retVal, )

0088

0089 @ans=retVal

0090

0091 return

0092

0093 *

0094 * Source Date: 08:15:23 08 JUN 1994 Build ID: AREV*3.1.11 Level:

The Sprezzatura Group

World Leaders in all things RevSoft

Thank you for responding…

I found the code for the W364 response on the knowledge base (after a long search), applied it and it works beautifully (with a lot of happy people).

The version is in fact v3.10. I first went to v3.12, but had the problem of "ghost" data images in several windows - actual data in database was fine, but the "ghost" data images drives personnel crazy….

The "meta compilation" error occured on v3.12 and v3.10 (on indexed fields). All of the databases are pure AREV (no MFS, rightdex or quickdex installed)

So, I guess my question is - Should I upgrade to the v3.12 and try to do something with the "ghost" data images? or stay at the v3.10 level and try to work around the other problems?

Any suggestions are appreciated!!!

If I recall correctly (not a sure bet these days with all the parity errors in my memory) the 'ghost' data images are caused by hidden prompt labels in the windows templates. Seems to occur mainly (but not always) AMV prompts.

You can either go into paint and 'unhide' the prompt labels, install the 3.12 patch and then go back into paint and hide the labels again.

Or

Aaron Kaplan posted the source for a utility program that scans through the Windows templates and strips out the 'hide label' marker.

I've only had mixed success using this utility but others have fared much better.

Mostly I've ended deleting the 'ghosted' fields and repainting them manually.

Try a search on "hidden" "hide" etc.

Leon-

I seem to recall the ghost data came from prompts with hidden labels that were too close to the edge of the screen- eg, if the label was hidden, the data fit on an 80 by 25 screen. If the label was visible, the screen would be 90 by 25, and the data skipped. ghosted, whatever. Any hidden labels?

Mike

Thanks All for responding..

The program from Spreaaztura Group did the trick on the "ghost" images on data entry…yes there were hidden prompts on other pages,

but the "ghosts" would appear on all pages and in different place - single value prompts, multi-value prompts, left side of page, middle,and right.

I am upgrading to the v3.12 tomorrow (06/27/01) and hopefully this will resolve the other promblems…

will keep you'all up to date..

Thanks again

I've found in 3.12 that you should unhide/show a prompt label before dragging/moving a prompt.

Mostly now I don't use hidden prompt labels and just use a ":" or some other character that I can superimpose another label over (e.g. Name: ).

Thanks all for responding and giving suggestions…

After upgrading to v3.12 from v3.10 and running the program from Aaron, it seemed to resolve 95% of the problems - no more "ghost" images, selection on index fields in a file did not return a "meta compilation" error. Finding the W364 resolution in the knowledgebase resolved the confirmation message - so most everything has been resolved - just 1 thing left -

The Ctrl-Z function does not work (will not reformat text to fit in a window)

View this thread on the forum...