|
Home > Archive > Programming with dBASE > March 2006 > Two dBase Executables
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Two dBase Executables
|
|
| Chris Faulkner 2006-03-11, 3:23 am |
| I have two separate Executables that I pass information to. So far I use a text file or dBase table. What I would like to do is pass in a memory variable. Is there a way that one EXE can see the others public variables
| |
| Ken Mayer [dBVIPS] 2006-03-13, 9:23 am |
| Chris Faulkner wrote:
> I have two separate Executables that I pass information to. So far I use a text file or dBase table. What I would like to do is pass in a memory variable. Is there a way that one EXE can see the others public variables
No, they can't. Memory variables, application properties, etc., belong
to the individual application and can't be shared. Imagine the chaos
that might ensue if one application changed values in another's
variables ... gad.
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/dbase/dBASEBook.htm
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase
| |
| Dave Colvill 2006-03-13, 8:23 pm |
| Ken Mayer [dBVIPS] Wrote:
> Chris Faulkner wrote:
>
> Save all memory variables to MEM file (save all to FILENAME.MEM)
at end of application No1 ( or during).
At beginning of 2nd program - restore from FILENAME.MEM additive.
Running 2nd prg after first will ensure all memory variables are available to 2nd prg.
| |
| Mervyn Bick 2006-03-14, 3:23 am |
| On Tue, 14 Mar 2006 02:27:02 +0200, Dave Colvill <davec@abb.on.net> wrote:
> Ken Mayer [dBVIPS] Wrote:
>
> Save all memory variables to MEM file (save all to FILENAME.MEM)
> at end of application No1 ( or during).
> At beginning of 2nd program - restore from FILENAME.MEM additive.
> Running 2nd prg after first will ensure all memory variables are
> available to 2nd prg.
The SAVE TO <file> LIKE command apparently has problems in selectively
saving variables so one would probably have to save the lot. It should be
possible to RESTORE selectively if this isn't broken too.
One would need to be very careful about adopting a shotgun approach to
saving and restoring public variables. It would be very easy to overwrite
something unintentionally.
Personally, I would rather not use a command that is known to be broken
and I would suggest that Chris sticks with his present system of saving to
text files or .dbf tables.
Mervyn
|
|
|
|
|