|
Hope you can clarify the following:
Our data-centre claims that NMAIL is (at this moment) an unsupported product.
If so, wouldn't that be a major risk provided that TPAS will actually use
this mailing facility.
If supported can you give me details were the support-organization
resides?
Is SQL required to enable inquiry on the local TPAS tables and the AMPs2-
database, or is it used when inquiring on the non-resident TPAS data.
SQL is not installed here.
Nijmegen will install ACMS V3.2 shortly. Any Problem for TPAS ?
Regards,
Ron Klaasse
|
| Ron,
�Our data-centre claims that NMAIL is (at this moment) an unsupported product.
True - NMail is unsupported. We will be using a distribution list,
placing the NM% in front of the name. The distribution list will be
easy enough to modify if need be or sites so desire. The advantage NMail
gives for mailing far out weighs the potential of non-support issues.
�Is SQL required to enable inquiry on the local TPAS tables and the AMPs2-
�database, or is it used when inquiring on the non-resident TPAS data.
�SQL is not installed here.
SQL will be required for reading, importing and updating the RDB
databases: TPAS$DB, TPAS$STKRM_DB, TPAS$XCLDD_DB.
All these databases will be local to sites with the first two being
supplied by the APPIX Organization in an SQL Export File Format.
�Nijmegen will install ACMS V3.2 shortly. Any Problem for TPAS ?
This should not be a problem. Currently we are developing against
V3.1 but will also be migrating to V3.2 in the Oct/Nov time frame.
Lois Magni
|