By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,495 Members | 1,110 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,495 IT Pros & Developers. It's quick & easy.

Access 2000 report opening, then closing immediately

P: n/a

I am having a problem with an Access 2000 report getting data from SQL
Server 2000. Here are the specifications for it:

RecordSource: a stored procedure (tested via query analyzer and working
correctly - permissions properly set)

InputParameters: just one - provided by a function call that is
functioning properly

When I run the report, it hits the Load event, runs the function to get
the input parameter, then immediately goes to the Close event. We had
similar behavior before, but that was due to the database owner not
being specified before the name of the stored procedure in the
RecordSource property. I have code inserted to run on Report Error, but
it isn't being triggered. I set a watch on Err to see if it changes
while the report runs, but it doesn't change.

Visually, the user doesn't see anything happen. The report never
actually appears on the screen. Codewise, it never hits the Activate,
NoData, Deactivate, or Page events.

I have pretty much run out of areas to look. I would appreciate any
hints, tips, or any words people might have to offer, even if someone
thinks it isn't relevant. Any experience similar to this might provide
me a clue to resolve this problem.

Thanks in advance for any assistance you might be able to offer.

Regards,
Rick Caborn
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Rick Caborn wrote:
I am having a problem with an Access 2000 report getting data from SQL
Server 2000. Here are the specifications for it:

RecordSource: a stored procedure (tested via query analyzer and working
correctly - permissions properly set)

InputParameters: just one - provided by a function call that is
functioning properly

When I run the report, it hits the Load event, runs the function to get
the input parameter, then immediately goes to the Close event. We had
similar behavior before, but that was due to the database owner not
being specified before the name of the stored procedure in the
RecordSource property. I have code inserted to run on Report Error, but
it isn't being triggered. I set a watch on Err to see if it changes
while the report runs, but it doesn't change.

Visually, the user doesn't see anything happen. The report never
actually appears on the screen. Codewise, it never hits the Activate,
NoData, Deactivate, or Page events.

I have pretty much run out of areas to look. I would appreciate any
hints, tips, or any words people might have to offer, even if someone
thinks it isn't relevant. Any experience similar to this might provide
me a clue to resolve this problem.

Thanks in advance for any assistance you might be able to offer.

Regards,
Rick Caborn


If I were in your place, I'd open up the report wizard and create a
quick, who-cares-how-it-looks report based on your current record
source. I would then run the report to see if it displays. If it
doesn't, then open up the recordsource and see if it displays. IOW, see
if the obvious is at fault.

If the report displays, then add the input parameter function. If it
fails, you know the source of the problem. BTW, you don't mention what
the input parameter is used for.

Without knowing what is the source of the problem it is hard to fix it.

I would do this step by step until the problem occurs....or I'd start
removing things until it starts working.
Nov 13 '05 #2

P: n/a
Rick Caborn wrote:
I am having a problem with an Access 2000 report getting data from SQL
Server 2000. Here are the specifications for it:

RecordSource: a stored procedure (tested via query analyzer and
working correctly - permissions properly set)

InputParameters: just one - provided by a function call that is
functioning properly

When I run the report, it hits the Load event, runs the function to
get the input parameter, then immediately goes to the Close event.
We had similar behavior before, but that was due to the database
owner not being specified before the name of the stored procedure in
the RecordSource property. I have code inserted to run on Report
Error, but it isn't being triggered. I set a watch on Err to see if
it changes while the report runs, but it doesn't change.

Visually, the user doesn't see anything happen. The report never
actually appears on the screen. Codewise, it never hits the Activate,
NoData, Deactivate, or Page events.

I have pretty much run out of areas to look. I would appreciate any
hints, tips, or any words people might have to offer, even if someone
thinks it isn't relevant. Any experience similar to this might
provide me a clue to resolve this problem.

Thanks in advance for any assistance you might be able to offer.

Regards,
Rick Caborn

I had something like this happen to me on what seemed a straightforward
report. It opened ok then when some old data was restored it would open
then shut immediately. Basically a case of bad data. The restored data was
using an older version of a table I had changed in the new version. Thus
the code couldn't execute probably and the recordsource and report never
came together and thus the problem.

Maybe something similar is happening to you...
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.