× Discuss about Archiving, Close of Business, Delivery Setup, Security Management System, Global Processing etc…

"No file name could be found for your query"

More
16 years 3 weeks ago #3352 by htaox
Hi all,

I have a VOC entry for FBNK.ACCOUNT like below:

File voc , Record 'FBNK.ACCOUNT'
Command->
0001 F
0002 ..\bnk.data\ac\FBNK_ACCOUNT
0003 ..\bnk.dict\F_ACCOUNT]D

When I do a simple "SELECT FBNK.ACCOUNT", I get a "No file name could be found for your query."

If I manually go to the physical location, I can JED the file with no issues. But it seems like the VOC entry is being ignored.

ANY SUGGESTION would really be greatly appreciated!
Thank you.

My remote.cmd looks like this:

set HOME=C:\bnk\bnk.run
set JBCRELEASEDIR=C:\jbase4\4.1
set JBCGLOBALDIR=C:\jbase4\4.1
set PATH=%PATH%;%JBCRELEASEDIR%\bin;C:\Program Files\Microsoft Visual Studio 9.0\VC\bin;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE
set JBCLOGNAME=bnk
set JEDIFILENAME_MD=VOC
set JEDIFILENAME_SYSTEM==%JBCRELEASEDIR%\src\SYSTEM
set JEDIFILEPATH=%HOME%

%JBCRELEASEDIR%\bin\jsh -s jsh -
exit

Please Log in or Create an account to join the conversation.

More
16 years 3 weeks ago #3354 by thisisavin
Replied by thisisavin on topic Re:"No file name could be found for your query"
Hi,
I assume that the voc entry is not right.
The underscore in the physical file name in the voc should be replaced with a dot "." i suppose.In other words check whether the physical file name and the name defined in the voc are the same. Hope that fixes your problem.

By the way what is the operating system you use?

regards,
dj

Please Log in or Create an account to join the conversation.

More
16 years 3 weeks ago #3355 by htaox
Hi,

The OS is Windows and the files do have underscores.
From jsh, I can jed into the files "..\bnk.data\ac\FBNK_ACCOUNT".

It just seems the VOC entry is being ignored when I do a "SELECT FBNK.ACCOUNT".

Thanks.

Please Log in or Create an account to join the conversation.

More
16 years 3 weeks ago #3357 by htaox
Hi thisisavin,

Apparently, the problem was caused by the version of jBASE I was using.

I was referencing jBASE 4 in the remote.cmd, but after installing jBASE 5 on a different server, and testing the same files, I was able to use "SELECT ..."

This issue has been resolved.
Thanks.

Please Log in or Create an account to join the conversation.

Time to create page: 0.034 seconds