Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!mephisto!mcnc!ecsvax.uncecs.edu!uncmed!boone!robinson
From: robinson@boone.med.unc.edu (Gerard A. Robinson)
Newsgroups: comp.databases
Subject: Re: Ingres/Net (5.0), heterogenous nets, and Vifred forms
Message-ID: <141@uncmed.med.unc.edu>
Date: 6 Feb 90 02:55:12 GMT
References: <GNB.90Feb5164436@baby.bby.oz.au>
Sender: news@uncmed.med.unc.edu
Reply-To: robinson@uncmed.med.unc.edu (Gerard A. Robinson)
Distribution: comp
Organization: UNC-CH School of Medicine, Office of Information Systems
Lines: 9

A work-around for this (which will lower performance slightly) is to
clear the iicompforms (I think that spelling is correct) table of the
'semi-compiled' version of the form.  This code incompatibility is what's
hitting you, depending upon the machine developed/used upon.  You'll
have to have different abf executable images anyhow, and the forms
(at least for OSL frames) are embedded in the application.  QBF frames
in ABF may be another story.

Gerard Robinson, UNC School of Medicine Office of Information Systems