Re: Power Object problems

In article <enduser-2611951554020001_at_204.247.5.30>, enduser_at_enduser.com (EndUser) wrote:

>this is good research, we have found a number of probs too.
>but we look at the version "1" and realize this is initial.
>surely you realize that the first users of anything must endure
>the bugs. to believe otherwise, is unwise, and unrealistic.
>overall, OPO v1, and what it promises is pretty neat.

Yes, I agree with you. In my behalf I could say that I waited 6 weeks for the package to be delivered (payed in advance for it and that was really UNWISE), had a tight schedule, hoped to have finally found the perfect database development environment (ok, that was even more unrealistic). And on top of this, the dealer asked me more money due to an error on his part !
Also note that I found these bugs in the first couple of hours I used OPO so I came abruptly back to reality and my reaction was a bit rude. Sorry. I do think this product is the future in the database market for the Macintosh platform, if you want to develop custom applications. Anyway, I found a couple more bugs and I post them to save some of you the time I wasted wondering if it was my fault or OPO's.

1. while you can paste text from OPO to another application, you cannot do the reverse
2. if you pass a string parameter to an external function its length get thrashed as in :

vString = SPACE(255) ' initialize string large enough to hold Str255 vRealLength = GetFile(vString,"PICT","TEXT","","") ' displays standard open dialog and returns file name and path in var vString, returns real length of string as a workaround
' now LEN(vString) is > 5000
vNewString= LEFT(vString,vRealLength) ' trim the string to real length

It's dirty work, but someone has to do it :-)

regards,

Daniele Toffetti
d.toff_at_sremo.sis.interbusiness.it Received on Sun Dec 03 1995 - 00:00:00 CET