FPD 2.6 Missing Procedures? 
Author Message
 FPD 2.6 Missing Procedures?
I have a program written in FPD2.6. I wrote a report to an already existing
program. When I execute this report, all runs ok, and the data is correct.
Then when I issue a "DO" command after exiting this report, to any of my
utility modules ("DO getpasswd") - kept in a utility.prg file which is part
of the project, I receive a message saying that the procedure cannot be
located?

Thanks
Steve



Sat, 14 Apr 2001 03:00:00 GMT
 FPD 2.6 Missing Procedures?

Sounds like you need to:

SET PROCEDURE TO utility.prg

--Paul

Quote:

>I have a program written in FPD2.6. I wrote a report to an already existing
>program. When I execute this report, all runs ok, and the data is correct.
>Then when I issue a "DO" command after exiting this report, to any of my
>utility modules ("DO getpasswd") - kept in a utility.prg file which is part
>of the project, I receive a message saying that the procedure cannot be
>located?

>Thanks
>Steve



Sat, 14 Apr 2001 03:00:00 GMT
 FPD 2.6 Missing Procedures?
Paul,

Thanks for the info.

Just a follow up if you don't mind.

Do you know why those utility programs are accessable before executing my
report and not accessable after?

Thanks
Steve


Quote:
>Sounds like you need to:

>SET PROCEDURE TO utility.prg

>--Paul


>>I have a program written in FPD2.6. I wrote a report to an already
existing
>>program. When I execute this report, all runs ok, and the data is correct.
>>Then when I issue a "DO" command after exiting this report, to any of my
>>utility modules ("DO getpasswd") - kept in a utility.prg file which is
part
>>of the project, I receive a message saying that the procedure cannot be
>>located?

>>Thanks
>>Steve



Sat, 14 Apr 2001 03:00:00 GMT
 FPD 2.6 Missing Procedures?
Paul,

Thanks again.

You nailed it, it was the "set procedure".

I setup a few break points, and checked the set procdure before entering my
module, procdeure was set, then after exiting the module, the procedure was
not set. This is a small module and there are no "set procedure" statement.
Do you know how this can be unset?

Thanks
Steve


Quote:
>Sounds like you need to:

>SET PROCEDURE TO utility.prg

>--Paul


>>I have a program written in FPD2.6. I wrote a report to an already
existing
>>program. When I execute this report, all runs ok, and the data is correct.
>>Then when I issue a "DO" command after exiting this report, to any of my
>>utility modules ("DO getpasswd") - kept in a utility.prg file which is
part
>>of the project, I receive a message saying that the procedure cannot be
>>located?

>>Thanks
>>Steve



Sat, 14 Apr 2001 03:00:00 GMT
 FPD 2.6 Missing Procedures?

Quote:
>Do you know how this can be unset?

Do you have a CLOSE ALL or a CLOSE PROCEDURE in your module?  Other than
that I can't think of what it could be.

Regards,

--Paul

Quote:

>Paul,

>Thanks again.

>You nailed it, it was the "set procedure".

>I setup a few break points, and checked the set procdure before entering my
>module, procdeure was set, then after exiting the module, the procedure was
>not set. This is a small module and there are no "set procedure" statement.
>Do you know how this can be unset?

>Thanks
>Steve



>>Sounds like you need to:

>>SET PROCEDURE TO utility.prg

>>--Paul


>>>I have a program written in FPD2.6. I wrote a report to an already
>existing
>>>program. When I execute this report, all runs ok, and the data is
correct.
>>>Then when I issue a "DO" command after exiting this report, to any of my
>>>utility modules ("DO getpasswd") - kept in a utility.prg file which is
>part
>>>of the project, I receive a message saying that the procedure cannot be
>>>located?

>>>Thanks
>>>Steve



Sat, 14 Apr 2001 03:00:00 GMT
 FPD 2.6 Missing Procedures?
Paul.

You nailed it again.

Yes I had a close all instead of a close databases and noticed that when the
command was issued that the "set procedure" variable was erased. Thanks
again.

Steve


Quote:
>>Do you know how this can be unset?

>Do you have a CLOSE ALL or a CLOSE PROCEDURE in your module?  Other than
>that I can't think of what it could be.

>Regards,

>--Paul


>>Paul,

>>Thanks again.

>>You nailed it, it was the "set procedure".

>>I setup a few break points, and checked the set procdure before entering
my
>>module, procdeure was set, then after exiting the module, the procedure
was
>>not set. This is a small module and there are no "set procedure"
statement.
>>Do you know how this can be unset?

>>Thanks
>>Steve



>>>Sounds like you need to:

>>>SET PROCEDURE TO utility.prg

>>>--Paul


>>>>I have a program written in FPD2.6. I wrote a report to an already
>>existing
>>>>program. When I execute this report, all runs ok, and the data is
>correct.
>>>>Then when I issue a "DO" command after exiting this report, to any of my
>>>>utility modules ("DO getpasswd") - kept in a utility.prg file which is
>>part
>>>>of the project, I receive a message saying that the procedure cannot be
>>>>located?

>>>>Thanks
>>>>Steve



Sun, 15 Apr 2001 03:00:00 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. FPD 2.6 Win XP Pro NTFS problem

2. FPD 2.6 and Win XP

3. Not a Table/DBF - FPD 2.6

4. FPD 2.6 mysterious record locks...

5. fpd 2.6 and the ESC key -

6. FPD 2.6 in W2K

7. FPD 2.6 Hang when browsing a table

8. Scrambling columns in BROWSE (FPD 2.6)

9. Help with .EXE for FPD 2.6

10. FPD 2.6 .exe issue - .prg compilation

11. Function Updated() and Push Button (FPD 2.6)

12. Jumb from FPD 2.6 to VFP 6.0


 
Powered by phpBB® Forum Software