A Microsoft Office (Excel, Word) forum. OfficeFrustration

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.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Using Forms
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

"Invalid argument" error message when trying to use a combo box



 
 
Thread Tools Display Modes
  #1  
Old June 19th, 2004, 05:58 PM
Tim
external usenet poster
 
Posts: n/a
Default "Invalid argument" error message when trying to use a combo box

I have an Access 2000 backend database on a Windows 2000
Small Business server. Front end is an MDE database. I
have a subform with a combo box that works fine on the
front end when working on the server, however when working
in the front end on a Windows XP computer the combo box
gives me the "invalid argument" error and there are no
options in the drop down box to select from. I have other
combo boxes on the same subform that work fine. Any
thoughts? Thanks.
  #2  
Old June 19th, 2004, 06:31 PM
Ken Snell
external usenet poster
 
Posts: n/a
Default "Invalid argument" error message when trying to use a combo box

Sounds to me as if the query that is the Row Source for the combo box has an
error when trying to use a function that is one of the query's fields.
Often, this can be because a Null value is the value of a field that is an
argument for a function that is being called.

You will need to check the query to see which functions it may be using, and
then check your data.

--

Ken Snell
MS ACCESS MVP

"Tim" wrote in message
...
I have an Access 2000 backend database on a Windows 2000
Small Business server. Front end is an MDE database. I
have a subform with a combo box that works fine on the
front end when working on the server, however when working
in the front end on a Windows XP computer the combo box
gives me the "invalid argument" error and there are no
options in the drop down box to select from. I have other
combo boxes on the same subform that work fine. Any
thoughts? Thanks.



  #3  
Old June 19th, 2004, 07:39 PM
Tim
external usenet poster
 
Posts: n/a
Default "Invalid argument" error message when trying to use a combo box


-----Original Message-----
Sounds to me as if the query that is the Row Source for

the combo box has an
error when trying to use a function that is one of the

query's fields.
Often, this can be because a Null value is the value of a

field that is an
argument for a function that is being called.

You will need to check the query to see which functions

it may be using, and
then check your data.

-- I'm not new to Access, but basically self taught and

not very knowlegable, so I'm not sure that I understand
your possible solution to the problem that I'm having. I
don't understand why the combo box works fine on a Windows
2000 computer but not on a Windows XP computer. Could the
problem be related to XP and not to the Row Source query?


Ken Snell
MS ACCESS MVP

"Tim" wrote in

message
...
I have an Access 2000 backend database on a Windows 2000
Small Business server. Front end is an MDE database. I
have a subform with a combo box that works fine on the
front end when working on the server, however when

working
in the front end on a Windows XP computer the combo box
gives me the "invalid argument" error and there are no
options in the drop down box to select from. I have

other
combo boxes on the same subform that work fine. Any
thoughts? Thanks.



.

  #4  
Old June 19th, 2004, 09:51 PM
Ken Snell
external usenet poster
 
Posts: n/a
Default "Invalid argument" error message when trying to use a combo box

Could be that the references are messed up on the Windows XP PC. If
references are messed up, functions may not work correctly and you can get
that Invalid argument message then, too.

Try following these steps (from a post by Douglas Steele, MVP):

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j....nceErrors.html


--

Ken Snell
MS ACCESS MVP


"Tim" wrote in message
...

-----Original Message-----
Sounds to me as if the query that is the Row Source for

the combo box has an
error when trying to use a function that is one of the

query's fields.
Often, this can be because a Null value is the value of a

field that is an
argument for a function that is being called.

You will need to check the query to see which functions

it may be using, and
then check your data.

-- I'm not new to Access, but basically self taught and

not very knowlegable, so I'm not sure that I understand
your possible solution to the problem that I'm having. I
don't understand why the combo box works fine on a Windows
2000 computer but not on a Windows XP computer. Could the
problem be related to XP and not to the Row Source query?


Ken Snell
MS ACCESS MVP

"Tim" wrote in

message
...
I have an Access 2000 backend database on a Windows 2000
Small Business server. Front end is an MDE database. I
have a subform with a combo box that works fine on the
front end when working on the server, however when

working
in the front end on a Windows XP computer the combo box
gives me the "invalid argument" error and there are no
options in the drop down box to select from. I have

other
combo boxes on the same subform that work fine. Any
thoughts? Thanks.



.



  #5  
Old June 22nd, 2004, 03:06 PM
Tim
external usenet poster
 
Posts: n/a
Default "Invalid argument" error message when trying to use a combo box

Thanks Ken. I checked the references to the extent that I
could since the database on the XP computer is an MDE. I
then put the MDB from the server onto the XP computer to
see if the combo box worked. It doesn't. I'm stumped!
-----Original Message-----
Could be that the references are messed up on the Windows

XP PC. If
references are messed up, functions may not work

correctly and you can get
that Invalid argument message then, too.

Try following these steps (from a post by Douglas Steele,

MVP):

This can be caused by differences in either the location

or file version of
certain files between the machine where the application

was developed, and
where it's being run (or the file missing completely from

the target
machine). Such differences are common when new software

is installed.

On the machine(s) where it's not working, open any code

module (or open the
Debug Window, using Ctrl-G, provided you haven't selected

the "keep debug
window on top" option). Select Tools | References from

the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in

front of them, unselect
them, and back out of the dialog. If you really need the

reference(s) you
just unselected (you can tell by doing a Compile All

Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference

at random, back out
of the dialog, then go back in and unselect the reference

you just added. If
that doesn't solve the problem, try to unselect as many

of the selected
references as you can (Access may not let you unselect

them all), back out
of the dialog, then go back in and reselect the

references you just
unselected. (NOTE: write down what the references are

before you delete
them, because they'll be in a different order when you go

back in)

For far more than you could ever want to know about this

problem, check out
http://members.rogers.com/douglas.j....ccessReference

Errors.html


--

Ken Snell
MS ACCESS MVP


"Tim" wrote in

message
...

-----Original Message-----
Sounds to me as if the query that is the Row Source for

the combo box has an
error when trying to use a function that is one of the

query's fields.
Often, this can be because a Null value is the value

of a
field that is an
argument for a function that is being called.

You will need to check the query to see which functions

it may be using, and
then check your data.

-- I'm not new to Access, but basically self taught and

not very knowlegable, so I'm not sure that I understand
your possible solution to the problem that I'm having.

I
don't understand why the combo box works fine on a

Windows
2000 computer but not on a Windows XP computer. Could

the
problem be related to XP and not to the Row Source

query?


Ken Snell
MS ACCESS MVP

"Tim" wrote in

message
...
I have an Access 2000 backend database on a Windows

2000
Small Business server. Front end is an MDE

database. I
have a subform with a combo box that works fine on

the
front end when working on the server, however when

working
in the front end on a Windows XP computer the combo

box
gives me the "invalid argument" error and there are

no
options in the drop down box to select from. I have

other
combo boxes on the same subform that work fine. Any
thoughts? Thanks.


.



.

  #6  
Old June 23rd, 2004, 03:07 AM
Ken Snell
external usenet poster
 
Posts: n/a
Default "Invalid argument" error message when trying to use a combo box

If you'd like, send me a small version of the database (zipped) and I'll
take a look. Include instructions as to which form, which combo box, etc.

My email address can be resolved by removing "this is not real" from the
reply address.

--

Ken Snell
MS ACCESS MVP

"Tim" wrote in message
...
Thanks Ken. I checked the references to the extent that I
could since the database on the XP computer is an MDE. I
then put the MDB from the server onto the XP computer to
see if the combo box worked. It doesn't. I'm stumped!
-----Original Message-----
Could be that the references are messed up on the Windows

XP PC. If
references are messed up, functions may not work

correctly and you can get
that Invalid argument message then, too.

Try following these steps (from a post by Douglas Steele,

MVP):

This can be caused by differences in either the location

or file version of
certain files between the machine where the application

was developed, and
where it's being run (or the file missing completely from

the target
machine). Such differences are common when new software

is installed.

On the machine(s) where it's not working, open any code

module (or open the
Debug Window, using Ctrl-G, provided you haven't selected

the "keep debug
window on top" option). Select Tools | References from

the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in

front of them, unselect
them, and back out of the dialog. If you really need the

reference(s) you
just unselected (you can tell by doing a Compile All

Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference

at random, back out
of the dialog, then go back in and unselect the reference

you just added. If
that doesn't solve the problem, try to unselect as many

of the selected
references as you can (Access may not let you unselect

them all), back out
of the dialog, then go back in and reselect the

references you just
unselected. (NOTE: write down what the references are

before you delete
them, because they'll be in a different order when you go

back in)

For far more than you could ever want to know about this

problem, check out
http://members.rogers.com/douglas.j....ccessReference

Errors.html


--

Ken Snell
MS ACCESS MVP


"Tim" wrote in

message
...

-----Original Message-----
Sounds to me as if the query that is the Row Source for
the combo box has an
error when trying to use a function that is one of the
query's fields.
Often, this can be because a Null value is the value

of a
field that is an
argument for a function that is being called.

You will need to check the query to see which functions
it may be using, and
then check your data.

-- I'm not new to Access, but basically self taught and
not very knowlegable, so I'm not sure that I understand
your possible solution to the problem that I'm having.

I
don't understand why the combo box works fine on a

Windows
2000 computer but not on a Windows XP computer. Could

the
problem be related to XP and not to the Row Source

query?


Ken Snell
MS ACCESS MVP

"Tim" wrote in
message
...
I have an Access 2000 backend database on a Windows

2000
Small Business server. Front end is an MDE

database. I
have a subform with a combo box that works fine on

the
front end when working on the server, however when
working
in the front end on a Windows XP computer the combo

box
gives me the "invalid argument" error and there are

no
options in the drop down box to select from. I have
other
combo boxes on the same subform that work fine. Any
thoughts? Thanks.


.



.



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 12:35 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.