|
Home > Archive > Getting Started with dBASE > October 2006 > same prg name in various directories
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 |
same prg name in various directories
|
|
|
| Having a prg in two separate directories, with the same name but with some variations between the two instances, it appears that after having executed the first instance in the first directory, then going in the second directory (with the navigator) and e
xecuting the second instance of the prg in there, the executed prg is the first one.
It should not, shouldn't it ?
Dom
| |
| John Marshall 2006-10-25, 7:23 am |
|
You are correct, that it should not, yet be sure that you have specified the full path and that you are not using an :Alias: that is causing the same procedure to fire.
PS: I also presume that if you are using "set procedure to" that you are assigning it to either different variables, locals, or releasing between calls.
JM
dlit Wrote:
> Having a prg in two separate directories, with the same name but with some variations between the two instances, it appears that after having executed the first instance in the first directory, then going in the second directory (with the navigator) and
executing the second instance of the prg in there, the executed prg is the first one.
>
> It should not, shouldn't it ?
> Dom
>
| |
| Ken Mayer [dBVIPS] 2006-10-25, 7:23 am |
| dlit wrote:
> Having a prg in two separate directories, with the same name but with some variations between the two instances, it appears that after having executed the first instance in the first directory, then going in the second directory (with the navigator) and
executing the second instance of the prg in there, the executed prg is the first one.
>
> It should not, shouldn't it ?
It's probably still in memory. It's a bad idea to do things like this if
you're going to be running things like that. Basically dBASE will keep
the file in memory unless you clear out memory ...
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
| |
|
| It happened accidentally because was working on a version of a prg to be installed on another machine. But anyway, I thought that even if DB keeps the pro in memory it should take the path in memory as well and recompile the prg.
Dom
Ken Mayer [dBVIPS] Wrote:
> dlit wrote:
nd executing the second instance of the prg in there, the executed prg is the first one.[color=darkred]
>
> It's probably still in memory. It's a bad idea to do things like this if
> you're going to be running things like that. Basically dBASE will keep
> the file in memory unless you clear out memory ...
>
> 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
| |
|
| Both were fired manually from the navigator or command window in a test session.
Dom
John Marshall Wrote:
>
> You are correct, that it should not, yet be sure that you have specified the full path and that you are not using an :Alias: that is causing the same procedure to fire.
>
> PS: I also presume that if you are using "set procedure to" that you are assigning it to either different variables, locals, or releasing between calls.
>
> JM
>
>
> dlit Wrote:
>
nd executing the second instance of the prg in there, the executed prg is the first one.[color=darkred]
>
| |
| bigMike 2006-10-25, 7:23 am |
| Although I don't think it should EVER happen, there have been times I have
seen where the re-compile does NOT take place - a rarity, of course, but
code can get lost that way and it's very upsetting.
bigMike
| |
| Ken Mayer [dBVIPS] 2006-10-25, 7:23 am |
| dlit wrote:
> It happened accidentally because was working on a version of a prg to be installed on another machine. But anyway, I thought that even if DB keeps the pro in memory it should take the path in memory as well and recompile the prg.
I wouldn't count on it.
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
| |
|
| This is not a satisfactory reply. I can see that on my own but it is against the concept of OODML. When I open 2 files with the same name in various directories, I must use the select a, select b to get them opened at the same time, otherwise, opening one
closes the other.
Dom
Ken Mayer [dBVIPS] Wrote:
> dlit wrote:
>
> I wouldn't count on it.
>
> 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
| |
| Ken Mayer [dBVIPS] 2006-10-25, 7:23 am |
| dlit wrote:
> This is not a satisfactory reply. I can see that on my own but it is against the concept of OODML. When I open 2 files with the same name in various directories, I must use the select a, select b to get them opened at the same time, otherwise, opening o
ne closes the other.
I am sorry you don't like my response. However, when dBASE opens a file
and it is in memory, that's the version that is in memory.
If you CLEAR MEMORY, it should resolve it ...
If you can't do that, then there's not much I can do for you here.
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
|
|
|
|
|