Welcome to the Birder's Diary Forum for Support And General Questions
Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.
Use the Community Sharing forum for sharing Photos, Trips, Stories, etc.
Setup your Forum photo and profile here.
Hello Jeff,
I tried to view a sightings report and get the attached error message. When I click on "OK" BD shuts down. I'm using BD5.1 ver 101 and Windows 10. This happens on any sighting report I choose.
Help, Al Borodayko
Cypress, CA
Hi Al, Thanks for posting and for the screenshot.
A couple questions:
- Does your UDF Need Better Photo still exist as a UDF?
- Are you choosing to output this UDF in your report? Is it listed as an output column?
If the UDF no longer exists, remove it from the output columns.
If it exists, and is selected as an output column; please remove it and test the report. If that works, then re-add this UDF as an output column and test again.
Thanks,
Jeff
My reports list Need Better Photo in the output column. I removed it and the report opened without the UDF. Then I closed the report and opened another one. That report opened. I was shocked that the Need Better Photo UDF was in the second report. So I re-opened the first report and this time the report opened with the Need Better Photo UDF as part of the report output.
I then realized I didn't save "Changes" when I deleted the UDF so the reports reverted to the original saved format.
Now the reports open properly. Guess the program needed a kick in the butt to get it's attention.
Anyhow, thanks for the help. All is good. The why is a mystery but that's your baileywick.
Regards, Al
Hi Al,
Not sure how that might have happened. But if you run into it again. Please post back here and we can try to chase it down.
Take care,
Jeff
UPDATE: Another customer had this same problem today with a Sightings report and a UDF column. The solution was the same. Remove and re-add the column and the problem went away.
If someone else experiences this and it is reproducible, I would love to get a copy of your database to test with. Please post here before you fix it.
Thanks,
Jeff
Update: Not sure how it got into this state, but if you receive this error.
- Start BD again
- Open the Report Designer window to the report type that you were working with (e.g. Sightings, LifeList, etc)
- Click on the Output Columns button and the table is refreshed and the issue is correct.
- You can now close the Output Columns pane and produce the report.
fyi
Jeff
Hello Jeff,
I don't know if you intended to fix the problem with the sightings report that includes UDF columns in BD 5.2, but I downloaded and installed BD 5.2v6 today and got the same error message as before (JUL 22 post). I followed your instructions from the AUG 24 post and the reports are now OK and the problem does not recur.
Everything else I looked at so far is working.
FYI, Al
Hi Al,
No, I am not sure what creates this problem, but I think it is the 'Database Upgrade' that occurs after you update your version of BD.
In either case, simply clicking on the Output Columns button fixes it. So low priority right now.
fyi
Jeff
This has been fixed in v5.2 Build 15; released 14 SEP 2020.
fyi
Jeff
