I concur that it would be great if the form definition could be downloaded
as an ASCII file that can be used to recreate the form, similar to the way
SYS_FORMS and SYS_REPORTS work(ed), I know it would have saved me a lot of
time.

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 MikeB
Sent: Saturday, January 04, 2003 1:50 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build
1.862

I can tell you one thing, I have had instances when the "Only" thing that
got me out of a "Problem" form was delete the damn form and create a new one
from scratch.  I can only guess the binary data that is in the make-up of
the form has the sniffles from some past event and reload/pack doesn't do
anything to recreate it.  In these instances, it would be great if the form
description commands could be generated in an ascii format (saveable to disk
and database) and would be simple to re-create the form.

----- Original Message -----
From: "Alastair Burr" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Saturday, January 04, 2003 1:19 PM
Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build
1.862


> I'm in W98SE and more often than not I have to re-boot but I usually do
> anyhow.
>
> I'm seriously considering putting Crashguard back in, though, it used to
> catch about half the crashes that I'm getting now and then I was able to
> save data and exit cleanly. At the moment every crash means losing
> everything that's not been saved which in turn means a reload at least if
> not a return to a backup. I'll try and hang on for a few more days just to
> see if anybody else turns up a solution. I really thought that the
clickable
> images was going to be the answer as I think I can probably say most
crashes
> occur when forms using them are or have been or are about to be in use.
>
> Maybe this particular form is just corrupted and needs to be re-created
but
> that's a long job but maybe I'll have to bite that particular bullet.
>
> Regards,
> Alastair.
>
>
> ----- Original Message -----
> From: "MikeB" <[EMAIL PROTECTED]>
> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
> Sent: Saturday, January 04, 2003 3:59 PM
> Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build
> 1.862
>
>
> >   If you are working in a Win9x environment, after a couple of crashes,
I
> > would "Absolutely" reboot the machine before continuing (you can't be
> > assured that that OS is cleaning up and reclaiming a possibly corrupted
> area
> > of memory that "May be Required" to perform the operation).
> >   If you are working in an "NT" kernel environment, I would "Probably"
> > reboot.....
> >
> >
> > ----- Original Message -----
> > From: "Alastair Burr" <[EMAIL PROTECTED]>
> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
> > Sent: Saturday, January 04, 2003 10:39 AM
> > Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build
> > 1.862
> >
> >
> > > Following Razzak's indication that the buttons on a form only work
with
> > BMP
> > > images - contrary to all the documentation - I amended the form that
> > seemed
> > > to be giving me the most problems.
> > >
> > > First of all, there is no obvious way of knowing what image, certainly
> > image
> > > type, that is used by a button. I have 5 buttons with with 5 JPG
images
> so
> > I
> > > created BMP copies then went to the form to change them:
> > >
> > > Object Manager | Forms | [select form] | Design
> > > Left Click on button (to ensure it IS selected) | right click on
> > Properties
> > > | Left click on Load Image | select the new BMP version | click on
Open
> |
> > > click on OK.
> > >
> > > Did it load the new version - who knows, it might have or it might not
> > > have - I have no idea. The image is the same so there is no visible
> > > difference.
> > >
> > > Repeat for the other 4 buttons  but the third one crashed R:Base when
I
> > > clicked on open.
> > >
> > > Start again and save the form between each change of image. Third one
> > > crashes R:Base again. This button is the same size as all but one of
the
> > > others in dimensions as well as file-size.
> > >
> > > Start again but commence with "difficult" button - R:Base crashes.
> > > Start again as before - same result.
> > > Move the old JPG images out of the directory so they cannot be used.
> > > Start again - manage to save the form this time but R:Base crashes
when
> > > closing the form designer.
> > > Start again - create a new button and open the new BMP image - at last
> > save
> > > it and exit without crash.
> > > Repeat with new buttons for other four items. Save form ok but R:Base
> > > crashes on exiting form designer.
> > > Start again, go to form designer and move an item a fraction and back
> > again
> > > then save form and exit without crashing!!!!!! The new buttons all
have
> > > their images and they must now be BMPs.
> > > Rename and then reload the database - no errors.
> > > Exit R:Base and remove the "pause for 2" from the app before the edit
> > > command.
> > > Start R:Base with the app - still crashes.
> > > Put the pause back in then give up and go to the pub - it's Sunday.
> > >
> > > Regards,
> > > Alastair.
> > >
> > >
> >
>
>

Reply via email to