Error 2448

[gtrudel]

I "inherited" an access app that manages a golf league. Each week, cards are produced depending on whether the league is playing the front or back. The report renders correctly and the data displays correctly. When I do a print preview I get the error 2448 with the error message on the code that puts the appropriate yardage in the first box. Here is the code:

Private Sub Detail1_Format(Cancel As Integer, FormatCount As Integer)
Dim db As Database
Dim rec As Recordset
Set db = CurrentDb
Set rec = db.OpenRecordset("course")
Dim x As Long
Dim y As Long
Dim holex As Long
If Me.[Front/Back] = 1 Then
holex = 0
Else
holex = 9
End If
With rec
Do Until .EOF


Select Case Left(rec!Hole, 1)
Case "b"
y = 0
For x = 1 To 9
Me("B" & x) = rec("[" & x + holex & "]")

The last entry is where the debugger stops. The cards are fine in the report view. The print and/or print preview has the issue

[ajetrumpet]

so it errors on the last line? define "last entry"

if so, the first thing I notice is that you're concating a string and a long. that shouldn't work, in theory.

[June7]

The concatenation can be done. Will it make sense?
This: "ABC" & 3456.7 will result in: ABC3456.7
This: "12" & "15" will result in: 1215
This: 12 & 15 will result in: 1215
This: "ABC" + 3456.7 will error
This: "12" + 15 will result in: 27
This: "12" + "15" will result in: 1215

This is because the + sign is holdover concatenation operator from ancient Basic as well as sum operator. Must be careful with it.

You are trying to dynamically build form control name and recordset field name or field index. I do this. Your syntax is wrong. Try: Me.Controls("B" & x) = rec.Fields("[" & x + holex & "]")

Is the x + holex to build a field name or field index?

[pbaldy]

I don't see a problem offhand. The + is adding two numeric variables to account for front or back 9 (golf terms), the & concatenation is putting brackets around what I assume is the field name (1-18, for the 18 holes). Error 2448 if I'm not mistaken relates to not being able to assign a value to the object. What are the controls named "B1", etc. If they're labels, they don't have a value property to assign (you can use the caption). If they're textboxes, what is the control source?

By the way, the reason it "works" in Report view is that the detail format event doesn't fire in Report view. I assume the boxes are not filled in?

[gtrudel]

Sorry - couldn't resist. The interesting aspect is that in report view all of the boxes are filled in. the control source for each box is a formula which displays the yardage for each hole depending on whether it is the front or back. Here is a sample - =IIf([Front/Back]="1","331","323"). This report replicates the cards from the course that contains the yardage from each of the marker - blue, white, red and the par for the hole. As I stated, the report renders just fine, but when I try to do anything from the print menu, I get the error "you can't assign a value to this object". Further, when I stop the debugger, I get a message stating that the "a custom macro in this report has failed and is preventing the report from rendering". Yet again, I can see all of the values in the report view. Thanks for the quick responses.

[June7]

Ooops! Just hit me that this code attempts to set value of a field or unbound textbox in a report. Don't think can do that. I have tried. Once a report starts to open, data can't be changed. The Detail_Format event can be used to modify display properties, such as make textboxes visible or not visible, but not set values of textboxes. You can call a custom function from a report textbox or refer to controls of an open form to get data.

[pbaldy]

The reason your code fails is because the textboxes have that control source. If you remove it, the code might work. You can set the value of an unbound textbox in the detail format event (just tested).

[June7]

I stand corrected. I just did a test also. Find that the value shows only in PrintPreview view. Guess I never tested that before. And, to my surprise, gtrudel's original syntax worked. Learn something new everyday. Seems there was some reason I had to use .Controls and .Fields in my project and will have to go back and verify that.

Also interesting that when I step debug I see the Detail_Format event is run twice.

So the issue is trying to change value of bound textbox.

[gtrudel]

Hi
First, thanks to all for the responses. Your comments pointed me to the properties on the detail report. The on-format property had the event procedure which pointed to the code that was abending. I removed this entry and the report rendered and printed correctly. THANKS again.

George

[pbaldy]

Glad you got it sorted out George. Basically you were trying to do the same thing 2 different ways and they conflicted with each other.