Programming with dBASE - dBASE Not Compiling Automatically

Author

dBASE Not Compiling Automatically

Jim Dutton

2005-07-21, 8:23 pm

I have another 2.5 problem: dBASE does not seem to be recompiling changed programs automatically. I have to issue the "compile" command explicitly to get changes to take effect. Has anyone else encountered this issue?

Ken Mayer [dBVIPS]

2005-07-21, 8:23 pm

Jim Dutton wrote:
> I have another 2.5 problem: dBASE does not seem to be recompiling changed programs automatically. I have to issue the "compile" command explicitly to get changes to take effect. Has anyone else encountered this issue?

Sometimes, yes. If you can toss together a proper turnkey (the code I'm
working on is so complex I couldn't turnkey it to save my life) for R&D,
they would most likely appreciate 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/GSP
http://www.goldenstag.net/dbase

Rick Gearardo

2005-07-22, 7:23 am

Hi Jim,

It happens mostly with data modules and menu files. I have not had a problem
with forms compiling in 2.5.

Rick

"Jim Dutton" <jtdutton@bu.edu> wrote in message
news:R%23wpXcjjFHA.1760@news-server...
>I have another 2.5 problem: dBASE does not seem to be recompiling changed
>programs automatically. I have to issue the "compile" command explicitly
>to get changes to take effect. Has anyone else encountered this issue?

Jim Dutton

2005-07-22, 9:23 am

I can't come up with a turnkey either. This is what was happening yesterday: I have a config file that runs when dBASE starts; it puts the various procedures I use in memory. I made a change in one of those procs, but when I typed "do config," the pre
vious version of the proc was run. I had to type the command "compile proclib" to make dBASE use the new file. This did not happen with previous versions. All in all, I am not happy with 2.5 and wish I had not upgraded.

Jim Dutton
===================

Ken Mayer [dBVIPS] Wrote:

> Jim Dutton wrote:
>
> Sometimes, yes. If you can toss together a proper turnkey (the code I'm
> working on is so complex I couldn't turnkey it to save my life) for R&D,
> they would most likely appreciate 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/GSP
> http://www.goldenstag.net/dbase

David Stone

2005-07-22, 11:23 am

Rick Gearardo wrote:

> It happens mostly with data modules and menu files. I have not had a problem
> with forms compiling in 2.5.

That's my experience too, although if a form has an OCX on it, it may not
auto-compile either (I haven't checked this in 2.5 yet). I think the latter bug
was recorded looooong ago.

David

Bruce Beacham

2005-07-22, 1:23 pm

Jim Dutton wrote:
> I made a change in one of
> those procs, but when I typed "do config," the previous version of
> the proc was run.

Perhaps insert this in your startup code:

set function F6 to "close procedure ; clear memory ;"

Then before re-running an edited program, hit F6.

You could add a call to the routine that sets the proc files if you need to.

Bruce Beacham

Gerald Lightsey

2005-07-22, 8:23 pm

On Fri, 22 Jul 2005 09:30:15 -0400, in the dbase.programming group, Jim
Dutton said...
> I had to type the command "compile proclib" to make dBASE use the new
> file. This did not happen with previous versions. All in all, I am
> not happy with 2.5 and wish I had not upgraded.

I suggest you take a look at HELP SET PROCEDURE and specifically at the
ADDITIVE and PERSISTENT qualifiers that were changed in 2.5. There is
information there regarding how to close.

Gerald

Ken Mayer [dBVIPS]

2005-07-25, 9:24 am

Jim Dutton wrote:
> I can't come up with a turnkey either. This is what was happening
> yesterday: I have a config file that runs when dBASE starts; it puts
> the various procedures I use in memory. I made a change in one of
> those procs, but when I typed "do config," the previous version of
> the proc was run. I had to type the command "compile proclib" to
> make dBASE use the new file. This did not happen with previous
> versions. All in all, I am not happy with 2.5 and wish I had not
> upgraded.

This is actually "normal" behavior, and has been that way for a long
time. The problem is that the routine is already in memory, and when you
re-run your configuration program, it sees the function or procedure in
memory and even though it recompiles the program, it doesn't re-load
that function or procedure, because it's already there.

You might add to the beginning of your configuration program something like:

clear all
release all
set procedure to program(1) additive

And see if that helps.

And yes, it did happen with earlier versions of the software, really.

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/GSP
http://www.goldenstag.net/dbase

Jim Dutton

2005-07-26, 11:23 am

Ken,
With all due respect (you have helped me a lot over the years), I don't think you are correct in this instance. To test my sanity, I went to another machine where version 2.2 is installed. There is the same config.prg file, calling a couple of procedure
s with "set procedure to ..." I made a small change (added a msgbox()) to one of the procedures, did not recompile explicitly, but simple typed "do config." The change showed up, meaning the called proc had been recompiled. I removed the msgbox, tried
again, and the msgbox didn't appear. So I think this does represent a change in v. 2.5. By adding "set procedure to" before listing the procs, I dealt with the issue (as suggested by someone on this forum).

Jim Dutton
===============
Ken Mayer [dBVIPS] Wrote:

> Jim Dutton wrote:
>
> This is actually "normal" behavior, and has been that way for a long
> time. The problem is that the routine is already in memory, and when you
> re-run your configuration program, it sees the function or procedure in
> memory and even though it recompiles the program, it doesn't re-load
> that function or procedure, because it's already there.
>
> You might add to the beginning of your configuration program something like:
>
> clear all
> release all
> set procedure to program(1) additive
>
> And see if that helps.
>
> And yes, it did happen with earlier versions of the software, really.
>
> 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/GSP
> http://www.goldenstag.net/dbase

Ivar B. Jessen

2005-07-26, 1:23 pm

<R#wpXcjjFHA.1760@news-server> datefromnewsgroupssu
bject

>I have another 2.5 problem: dBASE does not seem to be recompiling changed programs automatically. I have to issue the "compile" command explicitly to get changes to take effect. Has anyone else encountered this issue?

See OLH on SET DEVELOPMENT.

Ivar B. Jessen

Jim Dutton

2005-07-26, 1:23 pm

I have development set to "on."

================
Ivar B. Jessen Wrote:

> <R#wpXcjjFHA.1760@news-server> datefromnewsgroupssu
bject
>
> See OLH on SET DEVELOPMENT.
>
>
> Ivar B. Jessen

Ken Mayer [dBVIPS]

2005-07-27, 7:24 am

Jim Dutton wrote:
> Ken, With all due respect (you have helped me a lot over the years),
> I don't think you are correct in this instance. To test my sanity, I
> went to another machine where version 2.2 is installed. There is the
> same config.prg file, calling a couple of procedures with "set
> procedure to ..." I made a small change (added a msgbox()) to one of
> the procedures, did not recompile explicitly, but simple typed "do
> config." The change showed up, meaning the called proc had been
> recompiled. I removed the msgbox, tried again, and the msgbox didn't
> appear. So I think this does represent a change in v. 2.5. By
> adding "set procedure to" before listing the procs, I dealt with the
> issue (as suggested by someone on this forum).

This is an issue that I see fairly regularly. However, I think it occurs
more with forms and reports. It is possible that something has changed
in 2.5 ... since I wasn't directly involved in these changes, I didn't
test anything for R&D, and ...

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/GSP
http://www.goldenstag.net/dbase

Sponsored Links