ACCESS 2003 -- form and subform HELP........

Here is the actual SQL statement. I just want to make it simple so i
make a mistake on type it.

SELECT Student_financial_year.StudentID, Student_financial_year.year,
Student_financial_year.Applydate, Student_financial_year.PSAScomplete,
Student_financial_year.Totalincome, Student_financial_year.amountpay,
Student_financial_year.amountneed,
Student_financial_year.Totalmoneyaward,
Student_financial_year.Totalchildrens,
Student_financial_year.Totalchildrensstvm, Student_financial_year.GPA,
Student_financial_year.replacementtestresults,
Student_financial_year.Ranking, Student_financial_year.leadership,
Student_financial_year.religion, Student_financial_year.awardaccepted,
Student_financial_year.awardaccepteddate,
Student_financial_year.comment
FROM Student_financial_year
WHERE
(((Student_financial_year.StudentID)=[forms]![student]![studentid]) AND
((Student_financial_year.year)=[Forms]![student]![Student_Sub]![Student_financial_year
subform]![year]));

As i mention on the above, I don't think it've any errors on the
application. It's running fine when i run the application in ACCESS
2000 and ACCESS 2002 but it doesn't work when i run the same
application under ACCESS 2003 in XP.
It's giving me a popup and ask me to enter
[forms]![student]![studentid] and
[Forms]![student]![Student_Sub]![Student_financial_year subform]![year]
which it should get the value from the mainform calling this form. And
this form is the one run the SQL statenent above.
I just wonder is there any config that i need to know in ACCESS 2003 so
i can make it work like ACCESS 2000 or ACCESS 2002. Thank you for all
the advice but i doubt that there is anything wrong with the code
itself. The machine i run this application in ACCESS 2003, it've only
512 MB memory, is that the problem?

Here is the actual SQL statement. I just want to make it simple so i
make a mistake on type it.

SELECT Student_financial_year.StudentID, Student_financial_year.year,
Student_financial_year.Applydate, Student_financial_year.PSAScomplete,
Student_financial_year.Totalincome, Student_financial_year.amountpay,
Student_financial_year.amountneed,
Student_financial_year.Totalmoneyaward,
Student_financial_year.Totalchildrens,
Student_financial_year.Totalchildrensstvm, Student_financial_year.GPA,
Student_financial_year.replacementtestresults,
Student_financial_year.Ranking, Student_financial_year.leadership,
Student_financial_year.religion, Student_financial_year.awardaccepted,
Student_financial_year.awardaccepteddate,
Student_financial_year.comment
FROM Student_financial_year
WHERE
(((Student_financial_year.StudentID)=[forms]![student]![studentid]) AND
((Student_financial_year.year)=[Forms]![student]![Student_Sub]![Student_financial_year
subform]![year]));

As i mention on the above, I don't think it've any errors on the
application. It's running fine when i run the application in ACCESS
2000 and ACCESS 2002 but it doesn't work when i run the same
application under ACCESS 2003 in XP.
It's giving me a popup and ask me to enter
[forms]![student]![studentid] and
[Forms]![student]![Student_Sub]![Student_financial_year subform]![year]
which it should get the value from the mainform calling this form. And
this form is the one run the SQL statenent above.
I just wonder is there any config that i need to know in ACCESS 2003 so
i can make it work like ACCESS 2000 or ACCESS 2002. Thank you for all
the advice but i doubt that there is anything wrong with the code
itself. The machine i run this application in ACCESS 2003, it've only
512 MB memory, is that the problem?

The two parts of the WHERE clause:

((Student_financial_year.StudentID)=[forms]![student]![studentid])

I can't think why this is causing problems, unless your main form is not
called "student" and/or the control is not called "studentid".

((Student_financial_year.year)=[Forms]![student]![Student_Sub]![Student_financial_year subform]![year])

This one I don't understand, and I wouldn't have expected it to work in
any version of Access. The usual syntax for referring to a control on a
subform would be

Forms![Student]![StudentSub].Form![year]



On 17 Dec 2006 07:50:45 -0800, wrote:

Here is the actual SQL statement. I just want to make it simple so i
make a mistake on type it.

SELECT Student_financial_year.StudentID, Student_financial_year.year,
Student_financial_year.Applydate, Student_financial_year.PSAScomplete,
Student_financial_year.Totalincome, Student_financial_year.amountpay,
Student_financial_year.amountneed,
Student_financial_year.Totalmoneyaward,
Student_financial_year.Totalchildrens,
Student_financial_year.Totalchildrensstvm, Student_financial_year.GPA,
Student_financial_year.replacementtestresults,
Student_financial_year.Ranking, Student_financial_year.leadership,
Student_financial_year.religion, Student_financial_year.awardaccepted,
Student_financial_year.awardaccepteddate,
Student_financial_year.comment
FROM Student_financial_year
WHERE
(((Student_financial_year.StudentID)=[forms]![student]![studentid]) AND
((Student_financial_year.year)=[Forms]![student]![Student_Sub]![Student_financial_year
subform]![year]));

As i mention on the above, I don't think it've any errors on the
application. It's running fine when i run the application in ACCESS
2000 and ACCESS 2002 but it doesn't work when i run the same
application under ACCESS 2003 in XP.
It's giving me a popup and ask me to enter
[forms]![student]![studentid] and
[Forms]![student]![Student_Sub]![Student_financial_year subform]![year]
which it should get the value from the mainform calling this form. And
this form is the one run the SQL statenent above.
I just wonder is there any config that i need to know in ACCESS 2003 so
i can make it work like ACCESS 2000 or ACCESS 2002. Thank you for all
the advice but i doubt that there is anything wrong with the code
itself. The machine i run this application in ACCESS 2003, it've only
512 MB memory, is that the problem?

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.

Thank John for the reply......

I have a student form which contain the control name studentid. Inside
that form i have an subform which give me the Year. When the user
double click on the year it's calling another single form name
"Student_detail" which run from the Query as a control sourse.

It's working fine in any ACCESS version expet ACCESS 2003. When the
user double click on the year it's asking them to enter the StudendID
and the Year again before open the single form "Student_detail". I'm
not sure what is going on but I found this artical over the net. Is
that something i should do when run the application in ACCESS 2003 on
XP machice.

http://allenbrowne.com/bug-03.html

Thanks again. I hope someone have the same problems and they can show
me what i should do to make the application to run on ACCESS 2003.

On 17 Dec 2006 10:17:33 -0800, wrote:

Thank John for the reply......

I have a student form which contain the control name studentid. Inside
that form i have an subform which give me the Year. When the user
double click on the year it's calling another single form name
"Student_detail" which run from the Query as a control sourse.

That is what I assumed you were doing.

It's working fine in any ACCESS version expet ACCESS 2003.

Different versions of Access sometimes respond differently to
non-standard syntax or inputs. Have you actually tried any of the things
Daniel and I have suggested?

When the
user double click on the year it's asking them to enter the StudendID
and the Year again before open the single form "Student_detail". I'm
not sure what is going on but I found this artical over the net. Is
that something i should do when run the application in ACCESS 2003 on
XP machice.

http://allenbrowne.com/bug-03.html


It's certainly worth turning Name Autocorrect off. Having done so, make
certain that all the controls and fields still have the names you expect
them to have.

Having done that, I would delete the original query and create a new one
to return the data for the Student_detail form.


Thanks again. I hope someone have the same problems and they can show
me what i should do to make the application to run on ACCESS 2003.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.