Thanks Guys,
I was hoping that this was something stupid and/or simple that we'd done wrong but it obviously isn't. I'll have to go back to the drawing board to work out how to build the list of column names as part of the query building.
Hi lespaul,
My problem is that the application we've developed could be used with practically any type of database, therefore I need the column names to be returned the same way regardless of the database type that I'm connecting to.
Otherwise, I either need to get rid of the duplicated...
Thanks Skip,
Unfortunately, I use common code for several different databases and the users can add any fields that they want to the databases so generating a select that lists all of the fields will be a pain (though I'll do it if I have to!). What I'm really trying to get to the bottom of is...
Thanks,
But my problem is that I need all of the data to be present (this is a "normalised" view of three related tables) but I need to understand why the names given to the UniqueJobCode columns changes when I connect to SQL Server versus MS Access databases
Hi,
I'm working on a problem where we use the same SQL SELECT statement to create a normalised view of three tables (called "JOBS", "EXTRA" and "JOBSETTINGS"). All three tables use "UniqueJobCode" as their key.
The SQL statement we are using is:
SELECT * FROM ([JOBS] INNER JOIN [EXTRA] ON...
Hi,
I'm working on a problem where we use the same SQL SELECT statement to create a normalised view of three tables (called "JOBS", "EXTRA" and "JOBSETTINGS"). All three tables use "UniqueJobCode" as their key.
The SQL statement we are using is:
SELECT * FROM ([JOBS] INNER JOIN [EXTRA] ON...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.