stored procedure with paramater as rowsource

[Glenn Davy]

hi
Is it possible to have a storedprocedure with a parameter as a rowsource
to a combo/list box:
e.g.
me.cbMyCombo.rowsource='exec spMyLookup @Key=12345'

or

me.cbMyCombo.rowsource='spMyLookup 12345'

or

me.cbMyCombo.rowsource='spMyLookup(12345)'

etc
Tia
Glenn

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If using DAO: Put the EXEC statement in a pass-thru query. Use the
query as the ComboBox's RowSource.

- --
MGFoster:::mgf
Oakland, CA (USA)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBP7LD+4echKqOuFEgEQJZKQCgwQiv9XKCbi4v7DCJBOM2kH of73kAoI/r
F+IPQq7aeRk8CZnGe2o0RhUC
=bro5
-----END PGP SIGNATURE-----
Glenn Davy wrote:

hi
Is it possible to have a storedprocedure with a parameter as a rowsource
to a combo/list box:
e.g.
me.cbMyCombo.rowsource='exec spMyLookup @Key=12345'

or

me.cbMyCombo.rowsource='spMyLookup 12345'

or

me.cbMyCombo.rowsource='spMyLookup(12345)'

etc
Tia
Glenn

[Rich P]

based on the idea that a combobox can be based on either a table/query,
valuelist, fieldlist, I would say that with an sp you could either
populate a table in Access or create a Value list

cmd.CommandText = "yourSP"
cmd.CommandType = adCmdStoredProc
cmd.Parameters("@Parm1").Value = 123
Set RS = cmd.Execute

from here you could either populate a table or create your value list.
With ADO you could create a table in memory, but 2 things 1) is it worth
the work 2) I think the combobox needs to be based on a persistent table
(I think).

Rich

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Terry Kreft]

In principle it is a bad idea to dynamically build a value list as the
string space is limited.

If you ever think you need to do this then look at user defined rowsource
functions instead.

Terry
"Rich P" <rp*****@aol.com> wrote in message
news:3f*********************@news.frii.net...

based on the idea that a combobox can be based on either a table/query,
valuelist, fieldlist, I would say that with an sp you could either
populate a table in Access or create a Value list

cmd.CommandText = "yourSP"
cmd.CommandType = adCmdStoredProc
cmd.Parameters("@Parm1").Value = 123
Set RS = cmd.Execute

from here you could either populate a table or create your value list.
With ADO you could create a table in memory, but 2 things 1) is it worth
the work 2) I think the combobox needs to be based on a persistent table
(I think).

Rich

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!