third_party_content:community:commentary:forums_nonworks:faaa01cad0dae8198525669c0020737f

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 13 OCT 1998 01:54:27AM Jose wrote:

We have converted a system from ARev1 to ARev3 and run ARev 3:

    arev ,  /x /s /M4096

Speed: ARev3 is noticeably slower. It takes 3 times longer to display a customer record. Anyway to speed this up.

Reports: We a crucial report does the usual SELECT/LOOP:

    select customer by ... with ...
    printer on
    loop
        readnext @id ...
    while ..
        ...
        print customer.name 'L#20'
    repeat
    printer off

We get 100 records selected, but at the end the report says 890% done and 'No more rows available'. The report seems OK. Any reason for this?

Data Conversion/FMT: We get crashes with 'Non-numeric data when numeric expected'. Works OK in ARev1. Blanks seem to cause it - Are there any other forms of data causing the error?

Thanks


At 13 OCT 1998 09:53AM Victor Engel wrote:

I suspect the header of your file is currupted. Do a COUNTROWS file_name to reset the header.

If your windows are running slower, I suggest repainting them. This was a problem for us when upgrading to version 3.X, and nobody has ever been able to explain why the extra delay. However, if you repaint the screen, everything seems to work as normal. This is in addition to the delay you get from having to convert dots to underscores on the fly.

What is the context surrounding your non-numeric, etc. message?


At 13 OCT 1998 08:45PM Jose wrote:

Victor,

Thanks for your help. Re-painting the screens is a major task because of the hundreds of screens.

The Non-Numeric data problem turned out to be the conversion:

       FMT(amount, 'MD0')

of a field (amount) which was a multi-value instead of a single value.

The problem had been there for years, but ARev1 would handle it without crashing.

Jose


At 14 OCT 1998 08:35AM Victor Engel wrote:

Version 3 will handle that OK too. I guess it is what you do with the results that could be an issue. The results should also be multi-valued, and perhaps you were assuming otherwise?

Re: repainting screens. I suggest you at least test out my suggestion on one screen to see if it makes a difference. I've worked at a site where a delay of 1 to 2 seconds was completely eliminated by repainting the screen.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/faaa01cad0dae8198525669c0020737f.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1