Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Invalid Argument 1

Status
Not open for further replies.

zeldadawg

Technical User
Jul 5, 2001
6
US
When trying to create a Make Table query I am getting an "Invalid Argument" error message. After that I can not save any queries nor can I do any make table queries. The queries I am doing are using valid fields and tables. It will run as a query, however will not make a table nor will it save. It acts like the whole database is corrupted. The only way to combat the problem is to make a new database and export the tables to that database, however with 100+ tables and queries that is too many to export to new database.
 
I am an intermediate user of ACCESS and still not sure what you mean by writing the code. I am taking data from 2 joined tables to make another table. Now that I get the invalid argument I can only run the query, I can't save it nor can I make it a table.
 
When you use the Access interface to create a query, Access is creating the SQL statement that the computer uses to process your data. The graphic interface is just a user-friendly way of writing sometimes very complex SQL statements. To see the SQL of your query, open it in design mode and then click View on the menubar. Select SQL view. Copy the SQL code to the clipboard (Ctrl - C) and then paste it (Ctrl - V) into the message window on this forum. Seeing the SQL will allow others to see how your query is constructed and perhaps offer some solutions for you.

Uncle Jack
 
SELECT dbo_Temp_LatestLabtestDatesforAll.MRN, dbo_Temp_LatestLabtestDatesforAll.LabTest, dbo_Temp_LatestLabtestDatesforAll.LatestLabDate
FROM dbo_Temp_LatestLabtestDatesforAll;




Thanks for the help...
 
this select-statement seems to be okay. But it is not a make table query.

a make-table statement looks like this:

SELECT Table1.a, Tabel1.b INTO newtable
FROM Table1;

Where do fetch your data from: sql-server ? which version?

What do you do exactly, before the error occurs?

regards astrid
 
Are you saying:
You can successfully SELECT data from your SELECT query
until you try to make it a MAKE TABLE query? Then everything goes wrong.

Maybe Access does not know which data type to use when making a table: should a field be a number or text or what?

Have you ever used the APPEND query before?

Maybe if you design an empty table with particular data types, maybe you can append the SELECTION to it -
so it is a lot like doing a MAKE TABLE.

I really don't know though.

It would also be interesting to see if you can select just 1 field and make a table from it - then you might find that one field in the selection is the real problem and maybe that will inspire you.

Good Luck,

Mike
 
Maybe I am not putting this right. I have tables made already. I am selecting the table and querying on certain parts and trying to make another table. I have tried to take one field and make the query and that does not work either. Once I get the Invalid Arguement I can not save any queries nor can I do the make table query, nor can I import the queries and tables to another database. It is like it corrupts the entire database.
 
I know that this is an old post but I have had precisely the same problem - it started after I ran a make table query, and was intermittent thereafter - sometimes Access would allow me to save a query, and sometimes I would just get that annoying "Invalid Argument" message on trying to save. This continued after I deleted the table that I had made. Incidentally, all the other tables were not local, but just links to tables.

Eventually I created a new db, imported my linked tables again and copied my queries across. End of problems.

I appreciate that this is not an explanation!

HP
 
Following up: a possible explanation. The make table queries that I had run were substantial, and had pushed the file size of my db up to about 2 gig.

The new replacement is only 2 meg...

If you are used to working with linked ODBC tables rather than locally held ones you may not (as I did not) appreciate quite how much data they contain!

HP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top