I agree with those who would like access to a list of known bugs.
I also have struggled with entry/edit forms in RBWIN 6.5+ as well as
unrelated ODBC incompatibilities with Oterro. If I could have scanned a bug
list to see if my problems were due to something I was doing wrong or due
to a known bug it would have also saved me quite a bit of time.
Many of the major software development tools publishers (Microsoft, Lotus,
etc.) list their bugs and fixes for developers.
I also always thought pretty highly of the old Exchange "Problems and
Workarounds" section. It allowed developers to be forwarned of known
pitfalls that might be lurking. I know it also saved me many, many hours.
I understand that it would be very costly to print and distribute the
"Exchange", but an on-line version of just the "Problems and Workarounds"
would probably save the RBTI tech support team a significant amount of
support time and thus actually be a money saver for RBTI.
Tony
Anthony Schmidt
President
The Computery Ltd.
One East Main Street
Bay Shore, NY 11706
Voice 631-665-8100
Fax 631-969-5988
"Ben Petersen"
<advtech@2xtreme. To: [EMAIL PROTECTED]
net> cc:
Sent by: Subject: Re: Bug Listing
owner-rbase-l@son
etmail.com
05/10/2001 12:51
PM
Please respond to
rbase-l
When I first signed up for RDCC all reported bugs were viewable. It
was a bit much to just browse, but I figured at some point a
keyword search would be put into place (it would make for a great
trouble shooting tool). A few months later all I could see were my
own bug reports.
I always thought pretty highly of the old Exchange "Problems and
Workarounds" section. It allowed users to be forwarned of known
pit falls that might be lurking. I know it saved me many, many
hours.
Ben Petersen
On 10 May 2001, at 11:28, Craig Keenan wrote:
> Is there anywhere I can get a list of current bugs in the current (not
beta) build? Looked at rbase site, developers corner, documentation
included with software, nothing.
>
> Probably would save me weeks right now as I have already wasted a week on
the enter using..for 1 row problem that I requested help for earlier in the
week (now I'm sure it's a bug - I can't get it to add more than 1 row to
subsequent tables as advertised, even using the concomp db. Since
nobody responded to my original post, I'm pretty sure I'm not missing
anything...) also, thankfully I saw on this list that others noticed eep
only commands (saverow, nextrow, etc...) also don't work in RBWin, that one
had me befuddled there for a while too. I'm a month into converting a very
large system written in 4.5+ and would hate to scrap the whole thing - but
I can't keep running into brick walls.
>
> Any help is appreciated
>
> Craig Keenan
>
