pejacoby@mmm.serc.3m.com (Paul E. Jacoby) (04/26/91)
Is anyone else using the 4D Mover utility? I've been working with 4th Dimension 2.1.1 and have just started trying to use Mover to combine some databases. I am finding that everything I move results in a composite database which will cause a Bus Error in some fashion. Two examples: (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. (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. (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. I have Macsbug installed, and have found that the Bus Errors will generally cause the Mac to be totally incapacitated. In addition, on those occassions when I can get an 'ES' to kill 4D, the Finder will immediately implode with an "Illegal Instruction" error, and the machine will hang. I've talked to ACIUS, and they are "looking into it". Is anyone else having any LUCK with Mover? -- | Paul E. Jacoby, 3M Company | | | Maplewood, MN 55144-1000 | Parachuting? Why jump out of a | | => pejacoby@3m.com | perfectly good airplane? | | (612) 737-3211 | |
bmug@garnet.berkeley.edu (BMUG) (05/13/91)
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 | |