ADP Developed in Access 2007 opened in Access 2003?

[Brian Whiting]

I have a small user base with Access 2003 installed. I have an ADP file
developed in Access 2003 that connects to SQL 2005 Express. The ADP works
OK except for parameter queries ([enter Name] for instance). Those queries
are accepted as SQL code but will not open the dialog box to supply the
parameter value. I am assuming the problem is with Access 2003. I can get
a license for Access 2007 on a development machine to create the ADP file
with but probably cannot get funding for the user base to upgrade Access.
Can an ADP file created on Access 2003, opened and modified in Access 2007,
be opened and run on Access 2003? If not, does anyone know of a fix to
allow the parameter query dialog box to work in Access 2003?

 

[Tony Toews [MVP]]

I can get
a license for Access 2007 on a development machine to create the ADP file
with but probably cannot get funding for the user base to upgrade Access.

Note that the Access 2007 runtime is free and thus may work for you.

Microsoft Office Access 2007 Developer Edition FAQ
http://www.granite.ab.ca/access/developeredition2007faq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[aaron.kempf]

Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Thanks

Now regarding your problem-- I've never had a single problem with
parameters. But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

-Aaron

 

[Brian Whiting]

I don't use any variables that I know of in the applet. I don't use any VBA
code at all. Here is the query used to populate the form I am using:
SELECT AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID = Project.ProjID
WHERE (AssignedPeople.Name = '[Enter Name]')

If I use Jet as the back end, or use SQL 2000 a dialog will pop up to allow
a user to enter their name and get their worklist. With SQL 2005 the dialog
will not open so no Name goes in to be matched and the query returns
nothing.


Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Thanks

Now regarding your problem-- I've never had a single problem with
parameters. But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

-Aaron

 

[Brian Whiting]

I don't use any variables that I know of in the applet. I don't use any VBA
code at all. Here is the query used to populate the form I am using:
SELECT AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID = Project.ProjID
WHERE (AssignedPeople.Name = '[Enter Name]')

If I use Jet as the back end, or use SQL 2000 a dialog will pop up to allow
a user to enter their name and get their worklist. With SQL 2005 the dialog
will not open so no Name goes in to be matched and the query returns
nothing.


Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Thanks

Now regarding your problem-- I've never had a single problem with
parameters. But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

-Aaron

 

[aaron.kempf]

oh.. great stuff.

YES it _WILL_ prompt you.

If you have this SQL Statement as a sproc

CREATE PROCEDURE spFindPeople
(
@EnterName Varchar(50)
)
AS
SELECT AssignedPeople.*, Project.ProjID AS Expr1,
Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID =
Project.ProjID
WHERE AssignedPeople.Name = @EnterName

Now if you have a form.. that is bound to this procedure-- it will sit
there and prompt you for 'EnterName'.

Will it not? I've seen this functionality 100 times.. I just need more
information to be able to help you.
You say that you don't use variables..

Are you programming with VBA?

-Aaron

I don't use any variables that I know of in the applet.  I don't use anyVBA
code at all.  Here is the query used to populate the form I am using:
SELECT     AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM         AssignedPeople INNER JOIN
                      Project ON AssignedPeople.ProjID = Project.ProjID
WHERE     (AssignedPeople.Name = '[Enter Name]')

If I use Jet as the back end, or use SQL 2000 a dialog will pop up to allow
a user to enter their name and get their worklist.  With SQL 2005 the dialog
will not open so no Name goes in to be matched and the query returns
nothing.


Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Thanks

Now regarding your problem-- I've never had a single problem with
parameters.  But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
   Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

-Aaron

Note that the Access 2007 runtime is free and thus may work for you.

Microsoft Office Access 2007 Developer Edition
FAQhttp://www.granite.ab.ca/access/developeredition2007faq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems
athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/- Hide quoted text -

- Show quoted text -

 

[aaron.kempf]

are the sprocs the same on SQL 2000 and SQL 2005?

Can you give me the full code for the sprocs? or are you not using
sprocs?

Are you using 'InputParameters'?

I think that there are 20 different ways to use InputParameters.. I
just personally don't think that they are necessary for anything.

I would typically set the recordSource for a form programmatically to
be

EXEC spFindUsers ''

or
EXEC spFindUsers 'aaron'

I write a line of code that does that and it works like a charm.

Put a textbox on the form-- and when someone enters text in the box
(in the afterUpdate event)

put this code

Public Sub txtSearchPeople_AfterUpdate()
Me.RecordSource = "EXEC spFindUsers '" & me.txtSearchPeople & "'"
End Sub

That style of coding has always worked like a charm for me.. But I've
been writing Basic since 1982; so I don't really mind the VBA side

HTH-- Honestly

-Aaron

I don't use any variables that I know of in the applet.  I don't use anyVBA
code at all.  Here is the query used to populate the form I am using:
SELECT     AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM         AssignedPeople INNER JOIN
                      Project ON AssignedPeople.ProjID = Project.ProjID
WHERE     (AssignedPeople.Name = '[Enter Name]')

If I use Jet as the back end, or use SQL 2000 a dialog will pop up to allow
a user to enter their name and get their worklist.  With SQL 2005 the dialog
will not open so no Name goes in to be matched and the query returns
nothing.


Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Thanks

Now regarding your problem-- I've never had a single problem with
parameters.  But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
   Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

-Aaron

Note that the Access 2007 runtime is free and thus may work for you.

Microsoft Office Access 2007 Developer Edition
FAQhttp://www.granite.ab.ca/access/developeredition2007faq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems
athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/- Hide quoted text -

- Show quoted text -

 

[aaron.kempf]

and if you're _REALLY_ intent on doing it without code.. Id change it
to this

SELECT AssignedPeople.*, Project.ProjID AS Expr1,
Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID =
Project.ProjID
WHERE AssignedPeople.Name LIKE '%' + [Enter Name] + '%'

I think that will work like a charm.. I just noted that you had single
quotes around the '[EnterName]' parameter.

-Aaron

I don't use any variables that I know of in the applet.  I don't use anyVBA
code at all.  Here is the query used to populate the form I am using:
SELECT     AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM         AssignedPeople INNER JOIN
                      Project ON AssignedPeople.ProjID = Project.ProjID
WHERE     (AssignedPeople.Name = '[Enter Name]')

If I use Jet as the back end, or use SQL 2000 a dialog will pop up to allow
a user to enter their name and get their worklist.  With SQL 2005 the dialog
will not open so no Name goes in to be matched and the query returns
nothing.


Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Thanks

Now regarding your problem-- I've never had a single problem with
parameters.  But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
   Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

-Aaron

Note that the Access 2007 runtime is free and thus may work for you.

Microsoft Office Access 2007 Developer Edition
FAQhttp://www.granite.ab.ca/access/developeredition2007faq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems
athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/- Hide quoted text -

- Show quoted text -

 

[Brian Whiting]

Thanks! I will email this to myself at work and give it a try. When I put
[Enter Name] in the criteria block for query builder it put the single
quotes in automatically when it created the SQL query. I installed Access
2007 on a dev machine and tried the query as it was. I got the same result,
no records returned. This form of the query worked just fine against SQL
2000 with Access 2003. I don't know what an sproc is so I'm not knowingly
using them. I don't know how to bind anything to a form except a SQL query
via the design mode of the form.

and if you're _REALLY_ intent on doing it without code.. Id change it
to this

SELECT AssignedPeople.*, Project.ProjID AS Expr1,
Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID =
Project.ProjID
WHERE AssignedPeople.Name LIKE '%' + [Enter Name] + '%'

I think that will work like a charm.. I just noted that you had single
quotes around the '[EnterName]' parameter.

-Aaron

I don't use any variables that I know of in the applet. I don't use any
VBA
code at all. Here is the query used to populate the form I am using:
SELECT AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID = Project.ProjID
WHERE (AssignedPeople.Name = '[Enter Name]')

If I use Jet as the back end, or use SQL 2000 a dialog will pop up to
allow
a user to enter their name and get their worklist. With SQL 2005 the
dialog
will not open so no Name goes in to be matched and the query returns
nothing.


Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Thanks

Now regarding your problem-- I've never had a single problem with
parameters. But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

-Aaron

Note that the Access 2007 runtime is free and thus may work for you.

Microsoft Office Access 2007 Developer Edition
FAQhttp://www.granite.ab.ca/access/developeredition2007faq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems
athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/- Hide
quoted text -

- Show quoted text -

 

[BW]

I found some books online today and discovered the input parameter query for
Access 2007 has not changed any. I don't know why the brackets are not
prompting me. I did try your suggestion but SQL cannot parse the query
correctly without the single quotes around the [Enter Name]. I tried just
[Name] as well since that's the example the book I had gave, but it still
did not return any records. I think the problem must be something in the
SQL 2005 setup, although I have not been able to figure out what. I have
searched Google on this and have not seen anyone else report the problem.

Thanks! I will email this to myself at work and give it a try. When I
put
[Enter Name] in the criteria block for query builder it put the single
quotes in automatically when it created the SQL query. I installed Access
2007 on a dev machine and tried the query as it was. I got the same
result,
no records returned. This form of the query worked just fine against SQL
2000 with Access 2003. I don't know what an sproc is so I'm not knowingly
using them. I don't know how to bind anything to a form except a SQL
query via the design mode of the form.

and if you're _REALLY_ intent on doing it without code.. Id change it
to this

SELECT AssignedPeople.*, Project.ProjID AS Expr1,
Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID =
Project.ProjID
WHERE AssignedPeople.Name LIKE '%' + [Enter Name] + '%'

I think that will work like a charm.. I just noted that you had single
quotes around the '[EnterName]' parameter.

-Aaron

I don't use any variables that I know of in the applet. I don't use any
VBA
code at all. Here is the query used to populate the form I am using:
SELECT AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID = Project.ProjID
WHERE (AssignedPeople.Name = '[Enter Name]')

If I use Jet as the back end, or use SQL 2000 a dialog will pop up to
allow
a user to enter their name and get their worklist. With SQL 2005 the
dialog
will not open so no Name goes in to be matched and the query returns
nothing.


Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Thanks

Now regarding your problem-- I've never had a single problem with
parameters. But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

-Aaron

I can get
a license for Access 2007 on a development machine to create the ADP
file
with but probably cannot get funding for the user base to upgrade
Access.

Note that the Access 2007 runtime is free and thus may work for you.

Microsoft Office Access 2007 Developer Edition
FAQhttp://www.granite.ab.ca/access/developeredition2007faq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems
athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/- Hide
quoted text -

- Show quoted text -

 

[aaron.kempf]

Have you tried this format?

I know you can also do some stuff with the inputParameters; but I've
never found those necessary.
Because you stated you didn't want to try VB / VBA then we should look
at inputParameters if this @EnterName format doesnt' work

Thanks & Good Luck

-Aaron


SELECT AssignedPeople.*, Project.ProjID AS Expr1,
Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID =
Project.ProjID
WHERE AssignedPeople.Name LIKE '%' + @EnterName + '%'

I found some books online today and discovered the input parameter query for
Access 2007 has not changed any.  I don't know why the brackets are not
prompting me.  I did try your suggestion but SQL cannot parse the query
correctly without the single quotes around the [Enter Name].  I tried just
[Name] as well since that's the example the book I had gave, but it still
did not return any records.  I think the problem must be something in the
SQL 2005  setup, although I have not been able to figure out what.  I have
searched Google on this and have not seen anyone else report the problem.

Thanks!  I will email this to myself at work and give it a try.  When I
put
[Enter Name] in the criteria block for query builder it put the single
quotes in automatically when it created the SQL query.  I installed Access
2007 on a dev machine and tried the query as it was.  I got the same
result,
no records returned.  This form of the query worked just fine against SQL
2000 with Access 2003.  I don't know what an sproc is so I'm not knowingly
using them.  I don't know how to bind anything to a form except a SQL
query via the design mode of the form.

and if you're _REALLY_ intent on doing it without code.. Id change it
to this

SELECT     AssignedPeople.*, Project.ProjID AS Expr1,
Project.ProjName,
Project.Status, Project.DueDate
FROM         AssignedPeople INNER JOIN
                      Project ON AssignedPeople.ProjID =
Project.ProjID
WHERE     AssignedPeople.Name LIKE '%' + [Enter Name] + '%'

I think that will work like a charm.. I just noted that you had single
quotes around the '[EnterName]' parameter.

-Aaron

I don't use any variables that I know of in the applet. I don't use any
VBA
code at all. Here is the query used to populate the form I am using:
SELECT AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID = Project.ProjID
WHERE (AssignedPeople.Name = '[Enter Name]')
If I use Jet as the back end, or use SQL 2000 a dialog will pop up to
allow
a user to enter their name and get their worklist. With SQL 2005 the
dialog
will not open so no Name goes in to be matched and the query returns
nothing.
Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).
I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.
Thanks
Now regarding your problem-- I've never had a single problem with
parameters. But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.
Keep your variables in a table-- and you don't need to pass so much
junk around.
I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby
-Aaron
I can get
a license for Access 2007 on a development machine to create the ADP
file
with but probably cannot get funding for the user base to upgrade
Access.
Note that the Access 2007 runtime is free and thus may work for you.
Microsoft Office Access 2007 Developer Edition
FAQhttp://www.granite.ab.ca/access/developeredition2007faq.htm
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems
athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/-Hide
quoted text -
- Show quoted text -- Hide quoted text -

- Show quoted text -

 

[BW]

I tried it tonight and it worked just fine! Thanks for the tip!

Brian

Have you tried this format?

I know you can also do some stuff with the inputParameters; but I've
never found those necessary.
Because you stated you didn't want to try VB / VBA then we should look
at inputParameters if this @EnterName format doesnt' work

Thanks & Good Luck

-Aaron


SELECT AssignedPeople.*, Project.ProjID AS Expr1,
Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID =
Project.ProjID
WHERE AssignedPeople.Name LIKE '%' + @EnterName + '%'

I found some books online today and discovered the input parameter query
for Access 2007 has not changed any.  I don't know why the brackets are
not prompting me.  I did try your suggestion but SQL cannot parse the
query correctly without the single quotes around the [Enter Name].  I
tried just
[Name] as well since that's the example the book I had gave, but it still
did not return any records.  I think the problem must be something in the
SQL 2005  setup, although I have not been able to figure out what.  I
have searched Google on this and have not seen anyone else report the
problem.

Thanks!  I will email this to myself at work and give it a try.  When I
put
[Enter Name] in the criteria block for query builder it put the single
quotes in automatically when it created the SQL query.  I installed
Access 2007 on a dev machine and tried the query as it was.  I got the
same result,
no records returned.  This form of the query worked just fine against
SQL 2000 with Access 2003.  I don't know what an sproc is so I'm not
knowingly using them.  I don't know how to bind anything to a form
except a SQL query via the design mode of the form.

<[email protected]> wrote in message

and if you're _REALLY_ intent on doing it without code.. Id change it
to this

SELECT     AssignedPeople.*, Project.ProjID AS Expr1,
Project.ProjName,
Project.Status, Project.DueDate
FROM         AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID =
Project.ProjID
WHERE     AssignedPeople.Name LIKE '%' + [Enter Name] + '%'

I think that will work like a charm.. I just noted that you had single
quotes around the '[EnterName]' parameter.

-Aaron

I don't use any variables that I know of in the applet. I don't use
any VBA
code at all. Here is the query used to populate the form I am using:
SELECT AssignedPeople.*, Project.ProjID AS Expr1, Project.ProjName,
Project.Status, Project.DueDate
FROM AssignedPeople INNER JOIN
Project ON AssignedPeople.ProjID = Project.ProjID
WHERE (AssignedPeople.Name = '[Enter Name]')

If I use Jet as the back end, or use SQL 2000 a dialog will pop up to
allow
a user to enter their name and get their worklist. With SQL 2005 the
dialog
will not open so no Name goes in to be matched and the query returns
nothing.

Note that Tony doesn't know how to spell ADP and he constantly
reccomends people to move around from the best platform (ADP).

I would rather listen to George Carlins opinion of ADP than this
uneducated, unskilled chipmunk.

Now regarding your problem-- I've never had a single problem with
parameters. But I _SURE_ don't use prompts-- that spells of a poorly
written MDB application.

Keep your variables in a table-- and you don't need to pass so much
junk around.

I'd just reccomend this:
a) give us 10 times more information about 'how you're doing
parameters'.
Do you just bind a form to a sproc and hope for the best?
b) keeping your chin up and don't listen to this criminal MDB cry
baby

On Mar 23, 7:44 pm, "Tony Toews [MVP]" <[email protected]> wrote:

I can get
a license for Access 2007 on a development machine to create the
ADP file
with but probably cannot get funding for the user base to upgrade
Access.

Note that the Access 2007 runtime is free and thus may work for you.

Microsoft Office Access 2007 Developer Edition
FAQhttp://www.granite.ab.ca/access/developeredition2007faq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems
athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/-Hide
quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -