Replies

…or that the form has become corrupt? I haven’t had any go belly-up for a while, but it has happened in the past. The possible solutions were; reload a copy of the form from a backup or start a new form and copy all teh objects and code over to it.

I have to admit that I’m guessing but….

Do you have exclusive access to the database (ie. no-one else is logged on)?
Can you open it exclusively? (You’ll have to try the help system on this as I can’t remember, but I believe there is a startup option that you can use to give you exclusive control. You might want to see if that works is it may point to the problem. You may have to set up a batch file to startup the database using the the required startup option). Once you have logged on exclusively, then try to compact.

I have to admit that I’m guessing but….

Do you have exclusive access to the database (ie. no-one else is logged on)?
Can you open it exclusively? (You’ll have to try the help system on this as I can’t remember, but I believe there is a startup option that you can use to give you exclusive control. You might want to see if that works is it may point to the problem. You may have to set up a batch file to startup the database using the the required startup option). Once you have logged on exclusively, then try to compact.

Thanks macropod,
As you said, it’s probably not entirely satisfactory to open both workbooks. Not only that, but Excel’s display of a large text cell ain’t very pretty.
I’ve looked at a workaraound as per your suggestion. What I’ve decided to do is create RTF reports from Access and output them to a number of files. Then, in Excel, create a number of buttons to display the reports. It does look a bit nicer this way and it works, too.
Thank you for your help.

Excellent. Thanks Hans. Now I don’t have chase around looking any more. I had the same thing in Access 2000 so the limit must apply there too.
Thanks again.

And thank you for your efforts on this one, Charlotte.

Hi Charlotte,
Thanks for the suggestions.
1. Tried the requery – no effect.
2. Making the chart wider just makes the chart wider. You cannot see any difference in the lines and, although the scale changes on the X axis (so different date values are displayed on the scale) the date still ends up at the same place (short of the target).

Alas and alack. Woe is me.

Thanks for the info, Steve.
I have looked at Q317155 but I’m still at a loss.
There are two problems with this.
1. I’ve just checked someone elses workstation and this also happens on Win95.
2. I don’t know how to employ the workaround when the chart is on a form instead of a report. (There is no “On Format” event)
However, I do agree that a timing issue sounds reasonable.
Else, is it possible that some limit has been reached? (4000 rows on the chart?).
I have tried stretching the chart out (making it wider) but still no go.

D’oh!

The chart is a histogram type so at this scale it is a series of vertical lines. Maybe a pretty picture will help describe it (see attachment)?
The date range that I have picked is from 2002-02-01-01 (as per the left value on the X axis) to 2002-11-14-01 (x axis value stops at approx 2002-09-25-01 instead of 2002-11-14-01 and that’s the problem I am trying to address). So, yes, the date is one of the axes – the X axis.
Steve may have something in his reply post. I’ll try that. I am using Win2K on both my systems (Access97 and Access2000) so it is a possibility. I’ll also get someone on Win95 to try it out.
Will let you know.

Here’s hoping!

Thanks for your reply, Charlotte.
Unfortunately, the situation is not really applicable. I am not getting problems with updating the chart from one record to the next. I am having problems across the whole range that query has selected. Oh, and I don’t have any LinkMasterFields and LinkChildFields. I also tried this under Access 2000 and got exactly teh same thing. Let me try to clarify.
I have a query that lists data values across a stated date range (this is a concatenated value of YYYYmmddhh and is not strictly a date, just a number).
I have selected (using a form to take high and low values of the range) from 2002-02-01-01 thru to 2002-11-13-01 (without the dashes).
The query displays this whole range – some 4827 rows. The chart should display the same 4827 rows as data.
However, the chart based on this query only displays from 2002-02-02-01 to (approx) 2002-09-24-00;approx 4000 rows (I can’t tell the exact figure but it is pretty close and could be exact. Is this a “magic” number?). So it is starting at the correct point but is only displaying 4000 rows before stopping.
Maybe the other rows are “off the page” or something? If so, how do get it all back on the same page?
I don’t know. I’m guessing and totally frustrated.

I’d be guessing but I would think that you’d need to put the chart into teh DIVISION footer rather than in the FOOTER itself. Check your GROUPs and ensure you have a footer for DIVISION and place your chart there.
HTH.
PS. If this appears twice, I apologize. Somthing went wrong when SUBMITing. [sorry]

I’d be guessing but I would think that you’d need to put the chart into teh DIVISION footer rather than in the FOOTER itself. Check your GROUPs and ensure you have a footer for DIVISION and place your chart there.
HTH.

Hmmm,
Better late than never, I hope.
I used something like what’s below….

Me!chartPerf.hastitle = True
Me!chartPerf.charttitle.Text = “This is a title”

where chartPerf is the name of the chart.

HTH