G'day Razzak, At 01:31 17/10/02 -0400, you wrote:
At 07:31 AM 10/17/2002 +1000, you wrote:I have reported to RBTI a couple of issues that for me are show stoppers, I cannot distribute an app using the latest version of R:BASE if it contains these bugs and as they persist in this latest beta I don't know if RBTI can duplicate them.No, RBTI Cannot duplicate them. If they are, consider it DONE!
I spent 2 hours stripping out several forms, tables and code from my application in response to the request to provide a sample database for RBTI to replicate the problems. After doing so I spent further time testing to ensure that I was able to reliably replicate the bugs with that application and database. I then emailed it to the RDCC email provided for such and gave specific instructions and examples of how to replicate the bugs with the email.
I did that on the 8th of October and sent it to RBTI. To date I have received no reply to that email nor to the one I subsequently sent requesting data on whether RBTI were able to replicate the bugs using the sample database I sent.
You may want to create a CLEAN
Why the emphasis on CLEAN? Was my sample unclean in some way?
sample using CONCOMP database and then send it to R:DCC using the Concomp forms, reports, labels, etc. Your time and efforts will be greatly appreciated,
It's really, _really_ easy Razzak. All you have to do is take the YrsEmp form, put a call into the settings for the column EmpID to a block in an apx file that contains only one line, NEXTTAB. It will not move the cursor to the SalesInf table. It's not that difficult to replicate, honest! I just did it.
I would like to know if they are able to be duplicated in other environments than my own. If you have no forms that can test these issues I would be happy to send a sample database and app file I spent two hours creating last week with which RBTI could test. In the latest beta, 0. Many of the help messages I have entered for each field do not display. It is strangely sporadic. They will display in the status bar on some occasions and not on others. On a form with a tiered region containing about eight fields, three of them with eeps, the three with eeps do not display the help in the status bar. 1. The SKIP 1 function no longer worksTry the sample database R:DCC sent you to understand the functionality and the way of using SKIP 1 command in EEP.
That was not sent with the email I received.
I have a copy of that sample. Let me know if you want me to re-send it to you. Hopefully, it will help you understand.
I know I often bow to the superior knowledge of others on the list but when something that worked previously no longer works I do see how it is my lack of understanding that is the issue.
FYI, I have tested that sample myself and there is no problem with that.2. NEXTTAB no longer works. I have a two table form. The parent table has one field on the form which contains a call to a block that only has in it NEXTAB. It was working two betas ago but is now not.Same as above.
I repeat, it's _really_ easy Razzak. All you have to do is take the YrsEmp form, put a call into the settings for the column EmpID to a block in an apx file that contains only one line, NEXTTAB. It will not move the cursor to the SalesInf table. I've tested it. It does not work. It's not that difficult to replicate, honest!
I have personally tested that sample and these is no problem with that either.
Refer above. It is easily replicated in ConComp.
3. A field entry eep present in the first field is run when exiting the form from the last field in the row.Depends on the field order and field properties and anything else on the form, EEPs, App Files, etc.4. I have two forms with tiered regions that have a [PgDn] button on it of my own design that calls a playback file that has in it 20 [F8] key presses. On these two forms when I click the button the cursor moves down the valid number of rows but then moves up 16 or so lines and sits at line 2 or 4. If I press [F8] the cursor goes one row down from 20 to 21, so it appears as if the visual display is out of sync with the actual position.You need to create a SIMPLE reliable test using the CONCOMP database and then send it to R:DCC.
I do not understand this as an additional requirement when the previous requirement has been to send a small database to RBTI so they can replicate the problem. If it works in a simple manner and not in a more sophisticated environment that makes it no less a bug. I spent time I could ill afford in an attempt to make it as easy for RBTI as possible to reliably replicate the bugs. It is incredibly frustrating to then be told to "go reproduce them in ConComp" or "You need to create a SIMPLE reliable test using the CONCOMP database" when I have provided a sample database, as requested, in which the bugs are 100% replicable and therefore easily confirmed by someone who takes the time to look at the database. It does not work in at least two of my forms, period. They happen to be two of the most important ones for browsing data, persons and invoices. The bug does not appear to be due to an error in my code as it was working prior and is no longer. It is replicated in a database rebuilt from scripts generated with unload cmds. I do not have a simple app. It is large and complex in order to handle a multiplicity of requirements. If R:BASE can only be trusted to handle simple apps I am sorry if I mistook it for something it is not. Razzak I am _really_ peeved. And that is putting it mildly. I spent what for me was an arm and a leg twelve months ago upgrading to the latest and greatest R:BASE, LAN Pack, R:BASE Unlimited Multi-App Runtime, Oterro Unlimited Multi-App Runtime and I am unable to distribute my R:BASE app with anything other than what I had prior to the last upgrade. We are approaching the tail end of what I understand to be the last beta of the last patch prior to the unannounced release date of the new version 7 and I am concerned that the focus will totally switch onto version 7 leaving me high and dry. I am under continual pressure from some of my developers to move to another development environment that offers way more productivity enhancements and I am not a happy camper. You claim, "You will never regret staying current." I would really like to be in a position where I was able to endorse that philosophy but at present happy is about the last word I would use to describe my feelings towards RBTI's support for the latest and greatest. One of the advantages of dealing with a smaller vendor is that one likes to think that one's requirements are responded to more quickly and dealt with on a more personal level. (That is what I like to provide to my clients.) While I observe and acknowledge that this occurs to selected other people and for issues obviously more major to a majority, like the rounding one, that only makes it more frustrating when issues major to oneself are ignored, minimized or too-hard-basketed as not simple.
That's easy to say and sounds great from a PR point of view.Remember, if they are able to reliably replicate ANY submitted boo-boos on R:DCC, consider it FIXED! Once again, thanks for your efforts.
What I am wondering is, "Why is reality different from the PR?"
Why can I send a requested database to RDCC that is very easy
use for bug confirmation and no response forthcoming? Why can
I send 3 emails requesting inclusion to the Oterro beta testers
and no response be elicited until I email you personally? And
even then only to say that my request was noted.
What would be nice is if my efforts in bringing RBTI's bugs
to RBTI's attention were matched by a commensurate level of
RBTI bug squashing to bring about a reliable, stable product
instead of promises about things great in the future.
If I am expected to be planning\making future purchasing decisions
based on my current experiences with the product then my current
experiences are leading me elsewhere.
And I predict your response to that will be something along the
lines of "that is your right, R:BASE will move forward with or
without you."
So be it. But what a waste of potential.
JFYS are not the biggest fish in the ocean but we now have four
full time developers, two in training, one marketing assistant
and a quality control\testing and documentation person starting soon.
I just hate being forced into MS arms by over promises and under
delivery from someone I would prefer to support.
But, as you would say, "that is your right".
Warmest regards,
Tom Grimshaw
coy: Just For You Software
tel: 612 9552 3311
fax: 612 9566 2164
mobile: 0414 675 903
post: PO Box 470 Glebe NSW 2037 Australia
street: 3/66 Wentworth Park Rd Glebe NSW 2037
email: [EMAIL PROTECTED]
web: www.just4usoftware.com.au
"... the control of impulse -- is the first principle of civilization."-- Will Durant,
Pulitzer Prize winning philosopher, writer and historian
the most needed product in the world can be found at
www.thewaytohappiness.org
This email and any files transmitted with it are confidential to the intended recipient and may be privileged. If you have received this email inadvertently or you are not the intended recipient, you may not disseminate, distribute, copy or in any way rely on it. Further, you should notify the sender immediately and delete the email from your computer. Whilst we have taken precautions to alert us to the presence of computer viruses, we cannot guarantee that this email and any files transmitted with it are free from such viruses.
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
