Here is the master file for annualbils

FILENAME=ANNUALBILLS, SUFFIX=COM,$
SEGNAME=ANNUALBILLS,$
FIELDNAME=VENDOR_NAME,ALIAS=E1,USAGE=A50,ACTUAL=A50,$
FIELDNAME=BAN,ALIAS=E2,USAGE=A20,ACTUAL=A20,$
FIELDNAME=BILLING_CYCLE,ALIAS=E3,USAGE=A6,ACTUAL=A6,$
FIELDNAME=PYMT_SYSTEM,ALIAS=E4,USAGE=A4,ACTUAL=A4,$
FIELDNAME=INVOICE_DT,ALIAS=E4,USAGE=A10,ACTUAL=A10,$

You're using the ... DISK {path} form of FILEDEF, but {path} lacks a drive designation. It looks like a network location. Is this legitimate? I've always referenced a DISK location as 'C:\...' and never had a problem.

Are you sure the folder where annualbills.mas is located is in the APP PATH?

Also, you don't indicate what platform you're using. If your Reporting Server is UNIX or LINUX, filenames and masters can be case sensitive.

We are LINUX and all .fex, filenames, .mas and .acx files are lower case. For example, the file names annualbills.mas, ANNUALBILLS.MAS or AnnualBills.Mas would all name different files in UNIX or LINUX.

quote:

FILEDEF ANNUALBILLS DISK -
/users/1/nsuser/ibi/webfocus71/ibi_html/publish/cfo/annualbills.csv

In your filedef you need to be sure the 'drive' noted is one the application path recognizes. We have similar situations and all of our 'files' are on the 'd:' drive of the server. How is yours defined?

all very good suggestions. The main thing to think about is that when you TABLE FILE it is looking for the MAS in the app path. The FILEDEF is irrelevant for now.

An easy way to check this - from the WF Help files:

APP LIST app [HOLD] Lists the applications under approot.

If the HOLD option is used, it lists the applications under approot and writes the output to a temporary file called focappl.ftm, which you can then use in a report request.

APP QUERY app [HOLD] Lists all files in the application.

If the HOLD options is used, it lists all files in the application and writes the output to a temporary file called focappq.ftm, which you can then use in a report request.

If you can see your application folder and MAS file using the above commands, things are good. If not, change your path or move the MAS to a folder in the path.

Second, if the MAS is in the path, but the filedef is incorrect/invalid, you would not get this error. Instaead, it would run but you would get 0 records. If the data file is in a static location, the easiest thing to do is add a DATASET attribute in the MAS file (as described in the documentation.) Then you don't have to worry about doing a FILEDEF every time you need to use the file. The MAS always knows where its data is located.

I'd like to introduce a twist to this error. I used the SQL wizard to create a report which runs great before I add parameters. I added a couple parameters to support account # selection, etc using report options and the Where tab. When I run the report, I receive the same error above. The file name is "SQLOUT".

Using Dev Studio 7.62 on Windows XP with Server running on Linux SUSE10.

Thanks