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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Invalid Argument" Error 1

Status
Not open for further replies.

ckaspar

IS-IT--Management
Jun 5, 2003
51
US
I am having an error that I have never seen before.

When I try to select a selection form a combo box I get an error that says:

"Invalid Argument"

I am not given the opportunity to debug the code to see where the problem is. I am only offered "OK" and "Help" and buttons.

Please help me!

Thank you.

Chris Kaspar
Independent Systems and Software
Twin Town Treatment Centers
 
How are ya ckaspar . . . . .

Post the code for the Combobox! . . . We can tell alot from it!

Calvin.gif
See Ya! . . . . . .
 
This is happening in all of my databases
Have you tried to repair your office installation ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244
 
Alright. I thank you for your suggestions but I think I have narrowed it down to a corrupt record in one table.

My other databases were throwing the error as well because they are all linked to the primary database with the error on it, DUH!

So I have found the record but cannot delete it. I get the "Invalid Argument" error. I have tried exporting the table to Excel, deleting the record and re-impoting the table but I run into a real snag. I cannot have my regular Primary ID field be an Autonumber. I would have to reassign a new one. My ID field is linked to virtually everything in my databases.

What can I do to get rid of the corrupt record but keep the integrity there?

Chris Kaspar
Independent Systems and Software
Twin Town Treatment Centers
 
Ouch - another reason to avoid autonumbers, sorry, couldn't help it;-)

I suggest at least to create another field in the table, if it is possible, and update it to reflect the autonumber - then if everything goes real wrong, you could use/designate that field/number as a new primary key (and your own routine for creating autonumbers afterwards (faq700-184) - again, if everything else fails)

And BACKUP, BACKUP, BACKUP
(friend once told me, real men don't backup - but often cry...)

I haven't encountered this error/corruption myself, but here are some of the things (I think I remember) from threads on the topic here (in case it should happen).

I've seen some trying to append all data "below" this to a new table, then the data "above", but I don't know.

Also seen some say just take a copy of the table (ctrl+c, ctrl+v), then the new table would be OK cause Access won't copy the corrupted record (according to what I read).

Again, this is heresay, I'd suggest you also take the time to do some keyword searches here on Tek-Tips on he topic, websearch (Google...) and see what you can find.

Here are some links, the first one has lots of information on corruption, the second is a Microsoft link:
Corrupt Microsoft Access MDBs FAQ, How to Troubleshoot Corruption in a Microsoft Access Database

I wish you good luck!

Roy-Vidar
 
Well, After a day and a half of working on it I am back to normal.

Lesson learned hear backup everyday not just everyonce in a while.

Just so you guys know I had to copy the valid records to Excel then re-import them to a new table.

I the created a new Autonubmer, just for now, and had to reassign all of the fields from other tables attached to that autonumber field to the new autonumber field using n update query.

Thanks for the help guys

Then after some trial and error I hade to reassign some data types for my new table so that data was still valid in reports that I have created, dates primarily.

Chris Kaspar
Independent Systems and Software
Twin Town Treatment Centers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top