Please see comments below yours, Razzak, especially the one right at the
end:
----- Original Message -----
From: "A. Razzak Memon" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Friday, January 03, 2003 8:51 AM
Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build
1.862
>
> At 08:26 AM 1/3/2003 +0000, Alastair Burr wrote:
>
> >In the mean time does anybody else who is having these crashes have any
of
> >the following conditions:
> >
> >Is the form that might be the cause one that is based on a temp table?
> >Do you have any "set" commands that are database linked but with no
database
> >connected prior to calling the form? Or maybe ones that need the owner
> >password?
> >Do you have any other commands that return an error that you believe that
> >you can safely ignore prior to calling the form? Disconnect when there is
no
> >db connected, for example.
>
>
>
> Well Alastair.
>
> I think, you are answering your own questions. And, let me see if I can
> help you
> understand:
I'm clutching at straws trying to find something that might be the cause.
> 01. If the form is based on a TEMPORARY TABLE, you, as a programmer,
> need to make sure that the related TEMPORARY table exist before
> using the form.
>
> TEMPORARY TABLES are disappeared when the database is
> DISConnected.
>
> You will need to create startup file to re-define those temporary
> tables.
Yes, I know, the table definately is created first. The need for a pause
suggests a delay of some sort but everything I do to check that the table is
there confirms that it is created.
> 02. Use CVAL('Database')) option to return a text string
> containing the current connected database or NULL if
> the user is not connected to a database. This can be
> used to ensure that the user is connected before
> trying to execute some code. The example below shows
> how this might work.
>
> SET VAR vDB = (CVAL('Database'))
> IF vDB IS NULL THEN
> CONN MyDB
> ENDIF
>
> SET VAR vDB = (CVAL('Database'))
> IF vDB IS NULL THEN
> PAUSE 2 USING 'MyDB is currently unavailable'
> ENDIF
>
> The check is repeated to ensure that the attempt to
> connect to the database was successful before
> continuing with the command file.
Again, I know I'm connected and the table exists because after a short pause
it works and if I put a return before the edit command and go to thr R:> to
check the table and form work.
> 03. Make sure to pre-define all global variables used in forms with
> appropriate data type.
I believe that I've done this but, as always, I may have missed one. I doubt
it after all the checks that I've done but I'd be happy to find the answer
was as simple.
> 04. Use ENTER USING FormName or EDIT USING FormName at
> the R> prompt to make sure they work.
Works fine at the R:> - as it does in the app after a pause.
> 05. Make sure to SET MESSAGES ON and SET ERROR MESSAGES ON
> while testing and debugging your forms, reports, command files,
etc.
There are NO error messages or ordinary messages.
> 06. Use TRACE to narrow down the problem, if any, in your code.
The app runs through trace and RCode with NO errors every time.
> 07. If you are using any bit map buttons on form, make sure to use
BMP.
> (works better in 6.5++ for Windows)
****************************************************************************
*************
Now that might be a problem. I think they're JPGs. I seem to remember asking
about whether there was any preference and I think nobody came up with any
so I used the smallest files. Easy to change them and just the sort of thing
that _might_ be the cause. I'll let you know, probably tomorrow now.
****************************************************************************
**************
> Of course, 7.0 supports ALL kinds of buttons and graphics,
including
> maps and GPS coordinates.
As expected!!
> Hope that helps!
So do I - many thanks.
> Very Best Regards,
>
> Razzak.
>
Regards,
Alastair.
