Once you have adapted/acclimated to the GUI/event driven model, you will be able to create any behavior you wish.
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Ron > Peterson > Sent: Saturday, January 04, 2014 5:51 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: Converting Rules and other conversion issues > > After stripping the rules out of the structure file created with the > unload structure command, I found that all the table name references > were wrong. I edited them to the right table references and ran the > edited file and all the rules are now loaded properly. I have no idea > how the table reference names got changed in the unload structure but I > think there is a bug of some kind. I also had trouble with some views > not transferring. I unloaded each view from the 6.5 database using > list view and then edited each of them to create view (name) as select > .... and then ran each of the edited files and now all the views are > also in the new database. Thanks to a previous post, I unloaded and > reloaded the database in 6.5 and found a few corrupt records and fixed > them in 6.5 and now everything loads just fine in the 9.5 version. > The RB2 file is just under 500MB with almost 3 million records in 190 > tables and goes back to 1989. > > I want to thank everyone who took time to help me get to where the > converted database problems are solved. I have a lot of code changes > to continue with. Much of the program code dates back to the early > 1990's and there are many obsolete commands, etc., that now must be > fixed. Most of the old code was DOS based and so much is different > now. Dialog and Input used to allow the user to type over the old data > without having to delete or remove anything that was in the input > field. It was like the focus was on the field with all the data in the > field selected so a single keystroke would make all the old value go > away and being replaced with whatever was typed at the prompt. When > prompting for multiple values the screen showed the user what had > already been entered from the dialog or input prompts and now the > inputs from those commands is not visible without writing the response > back to the screen. I sure do miss that. > > Ron > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of MikeB > Sent: Saturday, January 04, 2014 3:32 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Converting Rules > > Project temp tTableName from sourctablename using * > > No constraints, no rules... :P > > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf Of Karen > > Tellef > > Sent: Saturday, January 04, 2014 11:56 AM > > To: RBASE-L Mailing List > > Subject: [RBASE-L] - Re: Converting Rules > > > > What the heck, let's stir the pot a bit. I don't like rules either, > > and try to replace with constraints whenever possible. That being > > said, sometimes I sorely miss being able to say "set rules off".... > > It's usually when I'm doing some batch processing from the r> prompt, > > or bringing in a dump of data that I know will temporarily break > > a constraint but I don't care. So much easier to set rules on and > off > > than altering a > > table to remove a constraint and then put it back on... > > > > The other day we added a column to a Payables table that already had > a > > constraint on it to limit what could be entered new. When I went to > > update the new column to insert values, got constraint errors on all > > the old rows... If it was a rule I could have simply turned the rule > > off. > > > > Karen > > > > > > > > -----Original Message----- > > From: Albert Berry <[email protected]> > > To: RBASE-L Mailing List <[email protected]> > > Sent: Sat, Jan 4, 2014 10:34 am > > Subject: [RBASE-L] - RE: Converting Rules > > > > > > I have a 280+ Mb database with no rules at all. I have triggers and I > > have constraints. > > Albert > > > > On 1/4/2014 5:41 AM, MikeB wrote: > > > I would chime in that if you haven't changed rules for constraints > > > where > > applicable, you should do that ASAP. Your life will be less > > complicated. My internal database is not huge, but my rules table > has > > only 5 rows. > > > > > > > > > > > > >
