Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!munnari.oz.au!murtoa.cs.mu.oz.au!ditmela!yarra!melba.bby.oz.au!leo!gnb From: gnb@bby.oz.au (Gregory N. Bond) Newsgroups: comp.databases Subject: Ingres/Net (5.0), heterogenous nets, and Vifred forms Message-ID: Date: 5 Feb 90 05:44:36 GMT Sender: news@melba.bby.oz.au Distribution: comp Organization: Burdett, Buckeridge and Young Ltd. Lines: 27 This may be my nomination for brain-damage-of-the-month award: Ingres/Net, vers 5.0/04, on Sun 3 and Sun 4 machines. The database is on a Sun 4 compute server. Forms created with vifred (and hence all abf applications) are NOT portable across architectures!!! So if I create a form using Vifred on a Sun4, and access it using qbf on a sun3. then qbf coredumps. Same thing if I use vifred on a sun3 and qbf on a sun4. So you have to have duplicates of all your forms, one for each architecture. And remember which one to ask for, depending which machine you are logged in to. And edit each form twice, once for each architecture. And you have to duplicate entire applications to build binaries for both architectures. Can someone tell me they fixed this brain-death in 6.0?? PLEASE? And why did it take RTI support 3 weeks to not find this out??? Greg. -- Gregory Bond, Burdett Buckeridge & Young Ltd, Melbourne, Australia Internet: gnb@melba.bby.oz.au non-MX: gnb%melba.bby.oz@uunet.uu.net Uucp: {uunet,pyramid,ubc-cs,ukc,mcvax,prlb2,nttlab...}!munnari!melba.bby.oz!gnb