Le mercredi 10 août 2005 à 09:17 -0400, Andrew Jensen a écrit : Hi Drew,
> Alex, > > True, this is the type of thing that everyday users want to do, and it > is just the type of thing that new users might get confused over. > However, I have to respecfully disagree with some of your conclusions. > Personally I can't name any db form designer that would do > exactly what Gary would want that wouldn't need a little 'glue' code, > "out of the box". (but there might be one) > Well, I seem to recall that I didn't need to do any scripting in Lotus Approach, yet I had two linked forms with automatic presentation of data from one and update of the other. > OooBase currently is quite capable of handling this in a very straight > forward and efficient manner - 'off the download'. I would not agree > that having to learn a few lines of Ooo Basic is a bad thing. Perhaps > the Basic library is a little more closely tied to the API then some > might like, > but things evolve. Doing what Gary wants to do most likely wouldn't > need more then 3 or 4 flines of code. I would say that is pretty good. > I'm not averse to learning OOoBasic, nor would I recommend that others not learn something about it, and my remarks certainly weren't intended that way. It's just frustrating as a user prior user of a graphical based solution that just worked out of the box after a few mouse clicks (FMPro comes to mind) to have to fight with Basic for something that seemed so easy before. This hasn't stopped me from reading the API, I'm in the slow process of translating it into French (part of the French n-l documentation effort), but there are concepts therein with which a lay computer programmer like myself feels completely at sea. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
