I thought that as long as the .sql file is included in the project's
build listing, the "source" .sql file would not be needed on the user's
machine, but the routine chokes with a message that somefile.sql does
not exist unless I put a copy of somefile.sql into the user's directory
in which the compiled application resides.

What am I missing here?

-------------------- Bill

From:	Ken Mayer [dBVIPS]
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 08:32:00 -0800

Bill P wrote:
> I thought that as long as the .sql file is included in the project's
> build listing, the "source" .sql file would not be needed on the user's
> machine, but the routine chokes with a message that somefile.sql does
> not exist unless I put a copy of somefile.sql into the user's directory
> in which the compiled application resides.
>
> What am I missing here?
>

..SQL files do not compile. There is no "somefile.sqo" for example ...

You need to include the .sql file either in the .exe, in the DEO path, etc.

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

From:	Bill P
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 11:27:36 -0600

Ken -

Could be I don't understand what you mean by "You need to include the
..sql file either in the .exe .........".

If you mean something other than including the .sql file name under
[Contents] in the .prj file, I don't know what to do.

--------------- Bill

Ken Mayer [dBVIPS] wrote:

>
> .SQL files do not compile. There is no "somefile.sqo" for example ...
>
> You need to include the .sql file either in the .exe, in the DEO path, etc.
>
> Ken
>

From:	Ken Mayer [dBVIPS]
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 09:36:03 -0800

Bill P wrote:
> Ken -
>
> Could be I don't understand what you mean by "You need to include the
> .sql file either in the .exe .........".
>
> If you mean something other than including the .sql file name under
> [Contents] in the .prj file, I don't know what to do.

Is the checkbox "Include file within executable?" checked on the File
Details page?

If is is, then all I can say is that it appears that the .SQL file needs
to be outside the .exe and available. I don't use .SQL files *EVER* in
my applications.

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

From:	Bill P
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 12:27:01 -0600

Ken -

Now I understand that I need to highlight the sql file in the project
listing and check that box. Hopefully, that will take care of the problem.

Would the alternative to referencing the sql files be to include
equivalent code in the wfms?

------------- Bill

Ken Mayer [dBVIPS] wrote:

> Bill P wrote:
>
>> Ken -
>>
>> Could be I don't understand what you mean by "You need to include the
>> .sql file either in the .exe .........".
>>
>> If you mean something other than including the .sql file name under
>> [Contents] in the .prj file, I don't know what to do.
>
>
> Is the checkbox "Include file within executable?" checked on the File
> Details page?
>
> If is is, then all I can say is that it appears that the .SQL file needs
> to be outside the .exe and available. I don't use .SQL files *EVER* in
> my applications.
>
> Ken
>

From:	Ken Mayer [dBVIPS]
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 13:47:40 -0800

Bill P wrote:
> Ken -
>
> Now I understand that I need to highlight the sql file in the project
> listing and check that box. Hopefully, that will take care of the problem.
>
> Would the alternative to referencing the sql files be to include
> equivalent code in the wfms?

That's what I do. If I use the SQL designer, which I seldom do, because
it's an annoying tool (it has some odd quirks, causes some odd problems
sometimes), I lift the SQL SELECT statement and work it into whatever
else I'm doing ...

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

From:	Bill P
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 12:48:14 -0600

Ken -

This did take care of the problem.

Many thanks.

--------------- Bill

Ken Mayer [dBVIPS] wrote:

> Bill P wrote:
>
>> Ken -
>>
>> Could be I don't understand what you mean by "You need to include the
>> .sql file either in the .exe .........".
>>
>> If you mean something other than including the .sql file name under
>> [Contents] in the .prj file, I don't know what to do.
>
>
> Is the checkbox "Include file within executable?" checked on the File
> Details page?
>
> If is is, then all I can say is that it appears that the .SQL file needs
> to be outside the .exe and available. I don't use .SQL files *EVER* in
> my applications.
>
> Ken
>

From:	Bill P
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 10:42:07 -0600

Ken -

The .sql files in question are included under [Contents] in the .prj
file used to build the .exe . Shouldn't that be sufficient?

Could it be something in the way the .sql is being referenced in the .wfm?

--------------- Bill

Ken Mayer [dBVIPS] wrote:
> Bill P wrote:
>
>> I thought that as long as the .sql file is included in the project's
>> build listing, the "source" .sql file would not be needed on the
>> user's machine, but the routine chokes with a message that
>> somefile.sql does not exist unless I put a copy of somefile.sql into
>> the user's directory in which the compiled application resides.
>>
>> What am I missing here?
>>
>
> .SQL files do not compile. There is no "somefile.sqo" for example ...
>
> You need to include the .sql file either in the .exe, in the DEO path, etc.
>
> Ken
>

From:	Ken Mayer [dBVIPS]
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 09:34:13 -0800

Bill P wrote:
> Ken -
>
> The .sql files in question are included under [Contents] in the .prj
> file used to build the .exe . Shouldn't that be sufficient?
>
> Could it be something in the way the .sql is being referenced in the .wfm?

Do you have it marked as being included in the .EXE?

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

From:	Michael Nuwer [dBVIPS]
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 12:37:15 -0500

Bill P wrote:
> Ken -
>
> The .sql files in question are included under [Contents] in the .prj
> file used to build the .exe . Shouldn't that be sufficient?
>
> Could it be something in the way the .sql is being referenced in the .wfm?
>

Here's what my prj file looks like when myTest becomes the exe file and
the sql file is linked into that exe:

[Contents]
C:\dBASETutorial\Source\Mytest.wfm,0,0,0,
C:\dBASETutorial\Source\Statements.sql,0,1,0,

From:	Bill P
Subject:	Re: Problem Re. .SQL files
Date:	Fri, 17 Dec 2004 12:28:54 -0600

Michael -

Thank you for the example.

I now see that this is what happens when the box is checked to include
the sql in the executable.

------------------ Bill

Michael Nuwer [dBVIPS] wrote:

> Bill P wrote:
>
>> Ken -
>>
>> The .sql files in question are included under [Contents] in the .prj
>> file used to build the .exe . Shouldn't that be sufficient?
>>
>> Could it be something in the way the .sql is being referenced in the
>> .wfm?
>>
>
> Here's what my prj file looks like when myTest becomes the exe file and
> the sql file is linked into that exe:
>
> [Contents]
> C:\dBASETutorial\Source\Mytest.wfm,0,0,0,
> C:\dBASETutorial\Source\Statements.sql,0,1,0,
>
>
>