Re: Mac front-end : Native versus cross-platform

In article <4gilu5$emp_at_newsbf02.news.aol.com>, noodles_at_aol.com (Noodles) wrote:

> We'll soon be starting a client server project designing a MAC front-end
> to an Oracle 7.1 database running OpenVMS 6.1 on an AXP. Does anybody
> have any experience with native or cross-platform developement ? We're
> thinking of using Powerbuilder or Oracle's Forms for the cross-platform
> tool. Are there any common pitfalls that we should be aware of ? I'm
> leaning towards native developement but I need some justification.
>
Native development tends to require less memory per performance unit than an equivalent cross-platform development. Also, native C programs tend to be more compact, faster, and memory efficient than those developed in a "front-end" tool.

Cross-platform development has two advantages: - it's cross-platform (duh)
- it's easier to get help with development (larger pool of resource to draw from)

I work in a Mac shop with about 1000 nodes on our net - about 1-200 hit the database at some time or another. 4D works pretty well, Appware is OK, Hypercard is OK. C or C++ is wonderful if you've got the developers.

Just my $.02 - Best wishes for your project.

David Scott                        ...how can I keep from singing?
                bumper snicker: My other guitar is a Martin (D16H)