Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!agate!garnet.berkeley.edu!bmug From: bmug@garnet.berkeley.edu (BMUG) Newsgroups: comp.sys.mac.apps Subject: Re: 4D Mover Bus Errors Keywords: 4D Mover 4th Dimension Message-ID: <1991May13.142412.729@agate.berkeley.edu> Date: 13 May 91 14:24:12 GMT References: <1991Apr26.134444.3327@mmm.serc.3m.com> Sender: root@agate.berkeley.edu (Charlie Root) Distribution: comp.sys.mac.apps Organization: University of California, Berkeley Lines: 35 In article <1991Apr26.134444.3327@mmm.serc.3m.com> pejacoby@mmm.serc.3m.com (Paul E. Jacoby) writes: > (1) Moving some procedures from one database to another, the > resulting database will Bus Error when I attempt to edit a procedure > which has been moved. Can't help you here; I assume you're talking about global procedures. I've never had problems editing moved global procedures. If this problem happens with only one of your moved procedures, you might try doing a copy-and-paste operation between the old database and a new procedure in the new database; if it's with all of them, something definitely weird is happening. > (2) Moving two databases into an empty database results in a Bus Error > in the new composite database when I switch files in the User > environment. Before you switch files in the User environment, you need to set default input and output layouts in Design. The defaults from your original databases aren't preserved in the move. > (3) Moving all elements of one database into an existing database results > in a Bus error in the composite database when I select a file which > was moved. Selecting a file that was already in the original database > causes no problems. This is probably the same problem as (2), with the same solution. Hope this helps! John Heckendorn -- /\ BMUG ARPA: bmug@garnet.berkeley.EDU A__A 1442A Walnut St., #62 BITNET: bmug@ucbgarne |()| Berkeley, CA 94709 Phone: (415) 549-2684 | |