If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
"Make Table" Issue
I have a "Make Table" Aggregate Query which is not producing the same data
consistently. Are there any known issues doing this? Never had to before, but if I use a Function to see if "TableExists"...find it, and Delete that Table before running the "Make Table" again, maybe that will produce consistent results?? TIA - Bob |
#2
|
|||
|
|||
"Make Table" Issue
Why would you do that. By default the make table query will overwrite an
existing one. If the is a problem then my guess is that it isn't in the making of the table. What exactly is the problem you are encountering. Is the data not correct? Is your query output not identical to your table data created by the make table query. Provide a little more info and we can 'think' with you on this one... -- Maurice Ausum "Bob Barnes" wrote: I have a "Make Table" Aggregate Query which is not producing the same data consistently. Are there any known issues doing this? Never had to before, but if I use a Function to see if "TableExists"...find it, and Delete that Table before running the "Make Table" again, maybe that will produce consistent results?? TIA - Bob |
#3
|
|||
|
|||
"Make Table" Issue
"Is your query output not identical to your table data created by the make
table query." ---- I'm not getting the "correct data" each time I run the Query making the table. Thank you - Bob "Maurice" wrote: Why would you do that. By default the make table query will overwrite an existing one. If the is a problem then my guess is that it isn't in the making of the table. What exactly is the problem you are encountering. Is the data not correct? Is your query output not identical to your table data created by the make table query. Provide a little more info and we can 'think' with you on this one... -- Maurice Ausum "Bob Barnes" wrote: I have a "Make Table" Aggregate Query which is not producing the same data consistently. Are there any known issues doing this? Never had to before, but if I use a Function to see if "TableExists"...find it, and Delete that Table before running the "Make Table" again, maybe that will produce consistent results?? TIA - Bob |
#4
|
|||
|
|||
"Make Table" Issue
On Thu, 31 May 2007 08:00:01 -0700, Bob Barnes
wrote: I have a "Make Table" Aggregate Query which is not producing the same data consistently. Are there any known issues doing this? Never had to before, but if I use a Function to see if "TableExists"...find it, and Delete that Table before running the "Make Table" again, maybe that will produce consistent results?? I'd simply delete the target table first (and trap the error if it's not there). Without knowing anything about your tables, the SQL of your query, or the nature of the error, it's more than a bit difficult to advise! One question though: why routine make-table queries? In my experience they are rather rarely needed; you can base a Form, a Report, an Export, even another Query on a select query. A MakeTable bloats your database, has a LOT of overhead creating new system table entries and indexes, etc. etc. - what purpose do these made tables serve? John W. Vinson [MVP] |
#5
|
|||
|
|||
"Make Table" Issue
John - Thank you.
I use the Table for a SQL statement in a module to Copy from Recordset in Access-to-Excel automation. I'm not at the Client today, but could Post that code next Tuesday when I'm there again. I know it works, but am willing to learn a better way. Bob "John W. Vinson" wrote: On Thu, 31 May 2007 08:00:01 -0700, Bob Barnes wrote: I have a "Make Table" Aggregate Query which is not producing the same data consistently. Are there any known issues doing this? Never had to before, but if I use a Function to see if "TableExists"...find it, and Delete that Table before running the "Make Table" again, maybe that will produce consistent results?? I'd simply delete the target table first (and trap the error if it's not there). Without knowing anything about your tables, the SQL of your query, or the nature of the error, it's more than a bit difficult to advise! One question though: why routine make-table queries? In my experience they are rather rarely needed; you can base a Form, a Report, an Export, even another Query on a select query. A MakeTable bloats your database, has a LOT of overhead creating new system table entries and indexes, etc. etc. - what purpose do these made tables serve? John W. Vinson [MVP] |
#6
|
|||
|
|||
"Make Table" Issue
On Fri, 1 Jun 2007 08:58:01 -0700, Bob Barnes
wrote: John - Thank you. I use the Table for a SQL statement in a module to Copy from Recordset in Access-to-Excel automation. I'm not at the Client today, but could Post that code next Tuesday when I'm there again. I know it works, but am willing to learn a better way. You can export from a Table to Excel. You can export from a Query to Excel. The two processes are identical, except that by exporting a query you save the extra step of creating a table. John W. Vinson [MVP] |
#7
|
|||
|
|||
"Make Table" Issue
You can export from a Query to Excel.
Will check it out...thank you - Bob "John W. Vinson" wrote: On Fri, 1 Jun 2007 08:58:01 -0700, Bob Barnes wrote: John - Thank you. I use the Table for a SQL statement in a module to Copy from Recordset in Access-to-Excel automation. I'm not at the Client today, but could Post that code next Tuesday when I'm there again. I know it works, but am willing to learn a better way. You can export from a Table to Excel. You can export from a Query to Excel. The two processes are identical, except that by exporting a query you save the extra step of creating a table. John W. Vinson [MVP] |
Thread Tools | |
Display Modes | |
|
|