MathGroup Archive 2008

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: Executing an external notebook within another notebook

  • To: mathgroup at smc.vnet.net
  • Subject: [mg93005] Re: Executing an external notebook within another notebook
  • From: Jens-Peer Kuska <kuska at informatik.uni-leipzig.de>
  • Date: Wed, 22 Oct 2008 05:41:06 -0400 (EDT)
  • Organization: Uni Leipzig
  • References: <gdja5r$ieh$1@smc.vnet.net>
  • Reply-to: kuska at informatik.uni-leipzig.de

Hi,

and you are too lazy to put the Mathematica program code
in a package and to write

Get["thePackageWithAllTheCodeINeed.m"]

Nobody need to execute a notebook from an other, because
all other people are able to split code and data/documents.

Regards
   Jens

Tugrul Temel wrote:
> Dear All,
> 
> Recently, the issue of executing a notebook within another notebook has
> arised and I worked on that for sometime. My progress has been limited and
> I am stuck at the following point.
> 
> 1) I wrote a generic "Common.nb" including the general code that can be
> executed using different data set.
> 2) I created another notebook "data.nb" retriving the data from Excel for
> calculations using the codes from "Common.nb"
> 3) I only open the "data.nb" and use Needs[] command to bring "Common.nb"
> to the current "nb" file, it gives a lot of errors.
> 4) If I only open the "Common.nb" and run it, it also gives errors.
> 5) However, if I open both "data.nb" and "Common.nb" and run them
> separately (the order of execution does not matter), then both programs
> run properly, giving the desired outcomes.
> 6) This shows that these two "nb" have somehow been linked to each other
> without my intention.
> 
> I do not know where I mass up. Please help me.
> 
> Regards,
> Tugrul
> 
> 
> 
> 


  • Prev by Date: Re: Is there a simple way to transform 1.1 to 11/10?
  • Next by Date: Re: Is there a simple way to transform 1.1 to 11/10?
  • Previous by thread: RE: Re: Executing an external notebook within another notebook
  • Next by thread: Controlling the order of evaluations