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.

Runtime error 3079 ...
Clear all

Runtime error 3079 with Always Only  


Eminent Member
Joined: 2 months ago
Posts: 34
September 7, 2020 2:30 pm  

I thought I would see if the Always Only feature works now. You may remember we discovered some time ago that it did not. I don't remember what it was doing then.

I tried it now with 5.2, and got Runtime error 3079: The specifed field GenusID , etc, etc. See the photo. This happened in 5.1 also.

If I do the UDF with "=", I do not get the error.

If I try Always Only in a report, (not the View Sightings window), I do not get the error. At least, not yet. Oh wait! I got a different error. Error in frmReportPreview2.CreateReport. The info is "-0". Then Runtime 364 Object was unloaded.

I guess this



means Always Only still needs some work. Does anyone use it? Have they had trouble? It would be a great feature because I do want a life list report that shows lifers that are only there because of a "heard' sighting. In other words, I have never actually seen the bird.

Member Admin
Joined: 2 months ago
Posts: 109
September 7, 2020 2:37 pm  

Hi David,

I need to remove this feature. As I worked on it for a long time and could not get it to perform well at all. A normal 1s query takes 60s+ with this Always Only query.

So for the time being, it is only there because I have not removed it.

Sorry about this, but I can't find a way to make it work efficiently.