[RBASE-L] - Criteria For My Unstableness With R:Base6.5++ Build 1.862

[Javier Valencia]

I have run into some of your problems at one time or another, and here are a few suggestions. In your forms and/or reports, go to design and make sure your variables do not show errors and that they are not redefined by eeps or code before the report/form is run. If you tried to modify the reports/forms with a previous version ( patch release) after the latest patch was installed, it seems to corrupt the forms/reports and they will work in a manner similar to the one you described. One problem that I was unable to track and RBTI tech support finally found was caused by a jpeg file (photo) that was displayed in a form at the beginning of the application and caused the application to crash much later; changing the way the photo was displayed fixed the problem, I still do not understand why a picture on the very first screen of the application would cause a crash hundreds (if not thousands) of lines into the application but apparently it did; and, as I indicated above, the workaround seems to have worked. Some things to look at include some of the settings such as NULL, ZERO, etc,. also, make sure that the files setting is set to a high number, I use 50 or 60 where the default is 5.   Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln., Suite #14 Olathe, KS  66062-4571 (913)829-0888 (913)649-2904 FAX   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Strickland Sent: Saturday, December 28, 2002 9:44 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Criteria For My Unstableness With R:Base6.5++ Build 1.862   This is a list of when the system crashes and I have tried this very same system on three different operating systems:   �         When I go into some forms and reports even from the >R prompt. �         When I use or input an extended where clause with a sort by it crashes every single time on all three systems. �         When I print a report with say 1 row of data after printing a report with 80 rows of data it crashes on all three systems.  But if I print a short report behind a short report or vice versa it seems to be stable. �         I did notice however, when I clean the database and input new data the system seems to be more stable but still crashes at times. �         I do have the same problem from the >R prompt with the above stated instances. R:Base has looked at this database and my code but seems to cannot duplicate my problem.  I became concern when I had three different systems to incur the same unstableness at for the most, the same area in programming.   I just wanted to know anyone else is experiencing this or has in the past?  Thank you.   Benjamin Strickland