Invalid Argument

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

HI- I have a large database in access- and all of a sudden I cannot add a new record or alter a record already in the database. When inputting new data I get an "invalid argument" message. (Invalid argument Error 3001: You tried to perform an operation that involves a routine DLL, and one of the arguments to the routine is invalid. Check your entry to make sure you specified the correct arguments, and then try to operate again. This error also occurs when you attempt to use mutually exclusive constants in an argument to a method, such as specifying both dbConsistent and dbInconsistent in the options argument to the OpenRecordset method.)

Could someone please turn that into english for me- and remember this just started happening- to something I have been working on for months- what changed. Thank You so muc
 
ITS said:
HI- I have a large database in access- and all of a sudden I cannot
add a new record or alter a record already in the database. When
inputting new data I get an "invalid argument" message. (Invalid
argument Error 3001: You tried to perform an operation that involves
a routine DLL, and one of the arguments to the routine is invalid.
Check your entry to make sure you specified the correct arguments,
and then try to operate again. This error also occurs when you
attempt to use mutually exclusive constants in an argument to a
method, such as specifying both dbConsistent and dbInconsistent in
the options argument to the OpenRecordset method.)

Could someone please turn that into english for me- and remember this
just started happening- to something I have been working on for
months- what changed. Thank You so much
Click to expand...

If you haven't been dooing any programming, just adding and modifying
data, this may be a sign that your database has been corrupted. See
Tony Toews' Corrupt Microsoft Access MDBs FAQ for diagnosis and recovery
tips:

http://www.granite.ab.ca/access/corruptmdbs.htm
 
I am looking into that- could it also be a size issue I have about 145 records all with graphics?

----- Dirk Goldgar wrote: ----

ITS said:
HI- I have a large database in access- and all of a sudden I canno
add a new record or alter a record already in the database. Whe
inputting new data I get an "invalid argument" message. (Invali
argument Error 3001: You tried to perform an operation that involve
a routine DLL, and one of the arguments to the routine is invalid
Check your entry to make sure you specified the correct arguments
and then try to operate again. This error also occurs when yo
attempt to use mutually exclusive constants in an argument to
method, such as specifying both dbConsistent and dbInconsistent i
the options argument to the OpenRecordset method.
just started happening- to something I have been working on fo
months- what changed. Thank You so muc
Click to expand...

If you haven't been dooing any programming, just adding and modifyin
data, this may be a sign that your database has been corrupted. Se
Tony Toews' Corrupt Microsoft Access MDBs FAQ for diagnosis and recover
tips

http://www.granite.ab.ca/access/corruptmdbs.ht
 
ITS said:
I am looking into that- could it also be a size issue I have about
145 records all with graphics?
Click to expand...

That doesn't sound like much, unless the graphics are large and with
high resolution. Access does store images very inefficiently, though --
you'll find a host of messages on the subject in this forum. How big is
your .mdb file, and what version of Access are you running? Access 97
has a maximum database size of 1GB, Access 2000+ of 2GB, and problems
usually start cropping up before you reach the maximum size.
 
I am working on Access 2000 and it is up to 1.99 GB ...Do you know the solution - I need to keep building this database- do I make a new table- then how do I link the tables together so they print in order- will I need to break up the catagories into seperate tables so when I make additions they are in order. I hope you can help- if it helps you to answer to know that this database is a catalog work in progress (meaning we keep adding new products) also when I link the tables am I going to be able to still have page numbers? I know how to use computers - but I don't know about computers- so simple answers are great. Thanks- I really appreciate your time

----- Dirk Goldgar wrote: ----

ITS said:
I am looking into that- could it also be a size issue I have abou
145 records all with graphics
Click to expand...

That doesn't sound like much, unless the graphics are large and wit
high resolution. Access does store images very inefficiently, though --
you'll find a host of messages on the subject in this forum. How big i
your .mdb file, and what version of Access are you running? Access 9
has a maximum database size of 1GB, Access 2000+ of 2GB, and problem
usually start cropping up before you reach the maximum size
 
ITS said:
I am working on Access 2000 and it is up to 1.99 GB ...Do you know
the solution - I need to keep building this database- do I make a new
table- then how do I link the tables together so they print in order-
will I need to break up the catagories into seperate tables so when I
make additions they are in order. I hope you can help- if it helps
you to answer to know that this database is a catalog work in
progress (meaning we keep adding new products) also when I link the
tables am I going to be able to still have page numbers? I know how
to use computers - but I don't know about computers- so simple
answers are great. Thanks- I really appreciate your time
Click to expand...

It's clear, then, that the size *is* your problem, and the problem is
almost certainly caused by the images you have stored in the database.
It arises because, although the image file you insert in your table may
be in a compressed format such as JPEG or GIF, Access always stores a
completely expanded bitmap of the image as well as the original picture
data. This leads to rapid bloating of the database. It *may* be that
you could recover some space in your database by compacting it (Tools ->
Database Utilities -> Compact and Repair Database...), but you will
always experience this bloating problem if you insert images into your
database in the normal way.

The simplest and most common solution to this problem is not to store
images in your database at all! Instead, store them in a particular
folder or set of folders on your hard disk, and store in the database
only the name -- or path and name -- of each image file, in text fields.
Then use unbound image controls, not OLE controls, on your forms and
reports to show the images. In the Current event of the form, and the
Format event of a report, use VBA code to set the image control's
Picture property to the path and name of the image file.

Larry Linson has a web page and demo database showing this method for
handling images, as well as two other methods, to be found here:

http://accdevel.tripod.com/imaging.htm

Let me know if you need more help with this.
 
Back
Top