Re: Power Object problems

the worst problem is that the blaze database cannot handle outside scripts which contain SQL. this makes the blaze only usefull for small tables, singly.

OPO must perform cross platform, in that light they have not adhered to all the mac conventions in terms of bitmaps and text, probably. for instance bitmaps are converted from the clipboard into .bmp files, a PCism. this is just something we macers will have to accept.

it would have been nice to have an xfcn interface, but the fact that they provided
a similar mechanism is adequate.

there are definite bugs in variable handling.

there are bugs in making standalones, it really doesnt work at all on the mac, and it crashes half the timeon the pc.

there are bugs in the debugger, and there are serious bugs in memory management. i can crash OPO by just creating my own menus, without building new ones, and try
to do any form processing.

there are shortcommings in the code editor. it is terrible not to have a search/replace
capability for long scripts. it is tedious to have to resize the property sheet all the time.

on the pc platform, i still cant get the first menu i append to appear first on the menu bar.

on and on. i am sure there are many others. but i have created a set of prototyping screens
for a large aerospace co., that are very impressive and beat out a parallel effort done by
twice the engineers using Ingres Open Road, they are still at it (est 3 mo more), i finished
last week.

--

In article <d.toff-0312951952130001_at_pcttym16.sis.interbusiness.it>,
d.toff_at_sremo.sis.interbusiness.it (Daniele) wrote:



> 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 :

> 

> DIM vString as STRING

> DIM vNewStr as STRING

> DIM vRealLength as   LONG INTEGER

> 

> 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