E
Edward
I've been asked to take over maintenance of a report generation tool.
It exists as a standalone app. that reports on a Pretty Large
Application.
The PLA is an Access MDB FE that links to a SQL Server BE, and the FE
has a smattering of local tables as well.
My reporting tool is an Access Project (ADP) that sits on the PLA's
SQL BE. But suddenly I happen to need data from a temporary Access
table in the application's FE.
What's worse, it needs it in a single SQL statement. To cut a VERY
unpleasant piece of SQL down to a manageable chunk...
SQL Table: PLA.tblApplicant
ACCESS Table: tblApplicantStatus
Requirement:
SELECT
tblApplicantStatus.fldStatus
FROM
tblApplicantStatus INNER JOIN PLA.tblApplicant ON
tblApplicantStatus.fldStatusID = PLA.tblApplicant.fldStatusID
Can it be done, with some trickery involving the prefixing the local
table with a connection string of some sort? Or am I doomed to
rewrite the whole shooting match as an MDB?
TIA
Edward
It exists as a standalone app. that reports on a Pretty Large
Application.
The PLA is an Access MDB FE that links to a SQL Server BE, and the FE
has a smattering of local tables as well.
My reporting tool is an Access Project (ADP) that sits on the PLA's
SQL BE. But suddenly I happen to need data from a temporary Access
table in the application's FE.
What's worse, it needs it in a single SQL statement. To cut a VERY
unpleasant piece of SQL down to a manageable chunk...
SQL Table: PLA.tblApplicant
ACCESS Table: tblApplicantStatus
Requirement:
SELECT
tblApplicantStatus.fldStatus
FROM
tblApplicantStatus INNER JOIN PLA.tblApplicant ON
tblApplicantStatus.fldStatusID = PLA.tblApplicant.fldStatusID
Can it be done, with some trickery involving the prefixing the local
table with a connection string of some sort? Or am I doomed to
rewrite the whole shooting match as an MDB?
TIA
Edward