I just got my second database working in Vantage 6.10.514. I also
was able to use a table from it in a Business Activity Query.
In my case, I changed only the Vantage.MFG file in the \mfgsys61
directory. I copied this file to the \prowork directory, which
contains only our custom programming stuff, so it can be easily
backed up and is not altered by Vantage upgrades.
The only line I changed in Vantage.MFG was:
ConnectOptions=-N TCP -H nts005 -S 6100 -ld MFGSYS
The new line is:
ConnectOptions=-N TCP -H nts005 -S 6100 -ld MFGSYS -db patriot -H
nts005 -S 6130
"patriot" is the name of the database, "nts005" is the host
and "6130" the service number. I could probably use the service
name, but didn't. I used the original INI file.
Once I logged into vantage, I used System Management, Vantage Basic,
Command window, then typed EDITPROG to start the Procedure Editor
from within Vantage. Next I selected Tools, Data Dictionary. At this
point, I got the warning that changing the MFGSYS database schema
would crash my session, followed by the message that this version
can't change the schema anyway. At this point, I can see that both
databases are connected. I exited back to Vantage.
Next, the cool part.
I went into the Business Activity Query, (Executive Analysis,
Business Activity Management, General Operations, Business Activity
Query), I built a query to list all the PartBin records in a small
warehouse, about 35 records.
I tested the BAQ as is, and it worked as expected. Since Vantage
does not "see" the second database, it is not affected by it, but,
on the other hand, it also does not help me to use it, so...
I editted the Query text to join it to my own table, a table of Part
Numbers that contains summary information about these part numbers.
Before:
for each PartBin Where PartBin.Company = cur-comp
and PartBin.WarehouseCode = 'FGA' no-lock:
After:
for each PartBin Where PartBin.Company = cur-comp
and PartBin.WarehouseCode = 'FGA' no-lock,
each Patriot.PartActSum Where Patriot.PartActSum.Company =
PartBin.Company
And Patriot.PartActSum.PartNum = PartBin.PartNum no-lock:
At this point the table is joined, but the BAQ fields menu does not
list my table. I select Add Calculation, and type
in "Patriot.PartActSum.OrderCount" in the window that opens. The
query passes analysis, and, when I run it, a column OrderCount
appears in the spreadsheet.
A couple of warnings:
I'm sure this sort of thing is not supported, so code in small
steps. Since you have to type in the query and field names, you will
need a good map of your database. In my case, I have my own version
of the Data Dictionary Viewer, which can display my database or
Vantage's in a format that looks a lot like Vantage's viewer.
was able to use a table from it in a Business Activity Query.
In my case, I changed only the Vantage.MFG file in the \mfgsys61
directory. I copied this file to the \prowork directory, which
contains only our custom programming stuff, so it can be easily
backed up and is not altered by Vantage upgrades.
The only line I changed in Vantage.MFG was:
ConnectOptions=-N TCP -H nts005 -S 6100 -ld MFGSYS
The new line is:
ConnectOptions=-N TCP -H nts005 -S 6100 -ld MFGSYS -db patriot -H
nts005 -S 6130
"patriot" is the name of the database, "nts005" is the host
and "6130" the service number. I could probably use the service
name, but didn't. I used the original INI file.
Once I logged into vantage, I used System Management, Vantage Basic,
Command window, then typed EDITPROG to start the Procedure Editor
from within Vantage. Next I selected Tools, Data Dictionary. At this
point, I got the warning that changing the MFGSYS database schema
would crash my session, followed by the message that this version
can't change the schema anyway. At this point, I can see that both
databases are connected. I exited back to Vantage.
Next, the cool part.
I went into the Business Activity Query, (Executive Analysis,
Business Activity Management, General Operations, Business Activity
Query), I built a query to list all the PartBin records in a small
warehouse, about 35 records.
I tested the BAQ as is, and it worked as expected. Since Vantage
does not "see" the second database, it is not affected by it, but,
on the other hand, it also does not help me to use it, so...
I editted the Query text to join it to my own table, a table of Part
Numbers that contains summary information about these part numbers.
Before:
for each PartBin Where PartBin.Company = cur-comp
and PartBin.WarehouseCode = 'FGA' no-lock:
After:
for each PartBin Where PartBin.Company = cur-comp
and PartBin.WarehouseCode = 'FGA' no-lock,
each Patriot.PartActSum Where Patriot.PartActSum.Company =
PartBin.Company
And Patriot.PartActSum.PartNum = PartBin.PartNum no-lock:
At this point the table is joined, but the BAQ fields menu does not
list my table. I select Add Calculation, and type
in "Patriot.PartActSum.OrderCount" in the window that opens. The
query passes analysis, and, when I run it, a column OrderCount
appears in the spreadsheet.
A couple of warnings:
I'm sure this sort of thing is not supported, so code in small
steps. Since you have to type in the query and field names, you will
need a good map of your database. In my case, I have my own version
of the Data Dictionary Viewer, which can display my database or
Vantage's in a format that looks a lot like Vantage's viewer.