Sounds like a mess!
1. You could convert everything to SQL, then just export to Access when
you need to if you are simply reporting from Access. Just a note,
access uses flat files and is much more inefficient compared to SQL
Server 2K. I would highly recommend converting everything to SQL
One CF datasource per query is what you get. However...
In Access, you can create a linked table to your SQL server tables.
In SQL Server, you can create remote servers, however, I don't know if
that includes Access databases, but if there is a driver for it, it
should work.
You will probably
Hello,
Some of our Access tables are being moved to our SQL
Server, while some remain in Access.
I have two datasources that separate the SQL from Access.
However, I run into some code
where tables from each of the datasources are in one
CFQUERY within a join.
Can I indicate multiple
You don't even have to do that. Just create ODBC datasources to your SQL
Server tables and edit your Access reports to use the SQL Server data. I
have a couple apps like this. Access does nothing more than provide forms
and reports. All data resides outside of Access.
-Original
maintain data w/o needing to create an entire web administration
interface just for one or two people.
M!ke
-Original Message-
From: Connie DeCinko [mailto:[EMAIL PROTECTED]
Sent: Friday, March 25, 2005 10:25 AM
To: CF-Talk
Subject: RE: Combininig Datasources in 1 CFQUERY
You don't even have
5 matches
Mail list logo
