Has anybody ever called WF from 1 sever to another server?
we have a server#2 with our history database around 10 MB and I would like to join some information from server#1 to server#2 without having to copy the DB from server#1 to server#2 every week
I have tried
SET BASEURL=SERVER#2.JIM.SHOE
TYPE=DATA,COLOR=RED,FOCEXEC=chuck_his.fex(NAME=B10),$ Which works great as a hyperlink
and I have tried

APP APPENDPATH \\SERVER#2\MASTAPP
FILEDEF AWARDS DISK E:\DBA\PERHIS\AWARDS.DAT

TABLE FILE AWARDS
WHERE RECORDLIMIT EQ 10
PRINT
NAME
END

OR

FILEDEF AWARDS DISK \\SERVER#2\DBA\PERHIS\AWARDS.DAT

TABLE FILE AWARDS
WHERE RECORDLIMIT EQ 10
PRINT
NAME
END

all these attemps are from SERVER#1 trying to call SERVER#2
Thanks Chuck.

WF 7.1.3

It is standard to have data on several servers/databases. The connections to the servers/databases are done in the Reporting Server Console. You cannot write a report to a datasource in a WebFocus focexec without the connectivity having been made previously.

Chuck

I regularly use fixed and focus files across servers with and without JOIN.

The only rules are having the mfd locally, in your case on SERVER#1, ensuring the machines are connected and that there is not a firewall in the way.

For Fixed format files I will use:

FILEDEF MYFILE DISK \\machineName\dirname\file.dat
TABLE FILE MYFILE
.
.

For FOCUS db files:

USE
\\machineName\dirname\file.foc as mymfd
END
TABLE FILE mymfd
.
.

If you were connecting to another type of data source, then N.Selph is correct and this would be set up in the console and acx files.

Thanks Alan & N.Selph
Do you know of any manuals that I can read up on to see if I am able to activate sever#2 from server#1.
I have tried the example you provide Alan with no luck, so I am thinking I need to some how connect to server#2 like N.Selph stated. I am trying to find out if there is a firewall on the 2 servers for which I think so due to we use server#1 for website reports.

Again thanks for your previous responses.

CnC,

As a test, try a:

DOS DIR \\machineName\directory
-RUN

from server#1 to server#2

check any firewall log on server#2 if you don't get a response.

I GOT
The network path was not found.

SO I AM THINK I HAVE THE WORNG MACHINE NAME.

That does sound like it!

That's the message that comes when a machine is not found.

Alan
I got it to work,,,, hurray
I did have the correct Machine Name but I was missing the drive name with the $ and I did not have a copy of the master for awards on MEM1, now I understand what you called MFD
FILEDEF AWARDS DISK \\SERVER#2\E$\DBA\PERHIS\AWARDS.DAT

But on the FOC DB I had to use APP FI HISTDB DISK \\SERVER#2\E$\PERHIS\HISTDB.FOC
plus place a DATASET statement in the master file DATASET = '\\SERVER#2\E$\PERHIS\HISTDB.FOC

Thanks for your suggestion

Great.

Something works!

Yes, of course, it does depend upon how a machine share is set up, I forgot about that bit.

I would have thought that the DATASET statement, the equivalent of the USE command, would be all that is necessary. A filedef, the APP FI, should not have any effect for .foc files.

And of course semantics play a large role here, MASTER FILE DESCRIPTION=MFD=MASTER=SYNONYM!

Hope everything goes smoothly for you.

Alan

You help me on this early in the year and it was working great. but the admin try to load WF 7.6 on server#2 but had problems and we went back to WF 7.13 and now my reports are not able to call server#2 anymore and was wondering if you have come across this problem before.

now when I try the DOS call test
DOS DIR \\server#2\E$\CPTEST
from server#1 I get Logon failure: unknown user name or bad password
but I can do the same call from server#2 to server#1 and it works fine.
do you know of any logs I can look at on server#2 to see why it keeps failing.

Thanks
Chuck

FYI, the techniques described above work great on Windows platforms but will not work on others because of the inability to map drives.

In that case you will need to use the -REMOTE syntax.