Hi Chuck,

Thanks for the database. I can indeed run reports without any issues. This confirms what I thought, but I just wanted to make sure. The problem with not with your database.

There is some corruption with your windows installation on this system. I cannot for the life of me imagine why a reinstallation won't fix that.

You said: as soon as the BD2eB file from eBird was put into my BD data, I edited that data so it looked like the other excel .cvs files. I do not understand what that statement means. BD2eB takes your eBird download (in this case) and puts it into BD CSV sightings import format. Then you are to use the BD Sightings Import feature to import that file. What do you mean you edited that data to look like the other excel files? In what way?

In either case, I can't imagine any way in which anything you did there would have caused any problem to BD.

SteveO - do you remember way back when another customer was having an issue like this with their reports? They were getting "[CommonName]" output on the report where it should have contained the actual common name (e.g. Blue Jay). I remember it happening, and feel that I remember it was resolved. However, I can't remember how or why.

Jeff

Hi Jeff,

Thanks.  What I meant about the BD2eB from eB to BD was that I did as you laid out.  Downloaded from eBird, it was formatted by BD2eB and then I imported it into my database, using the EB import option.

About the editing I did.  For some time I've been exporting my files to Excel, saving them as .csv files and then importing them in batches to eBird.  To do that with the detail I wanted, I edited my export so that it conformed to eBird's requirements, and it's been working flawlessly.  With the new data, I imported into BD, I then simply edited the BD file to have the same info as a file I'd import into eBird, even though I know I'll never need to export that data to eBird since it's already there - it's not very rational, but it satisfied my OCD tendencies.

I'll check out what reinstalling Windows might do.

Chuck

Thanks for the info Chuck.

If you can/will reinstall Windows, I would bet that BD has to certainly start working after you install it. Be sure to keep a copy of your database(s) offline.

The symptoms seem to indicate that you encountered some sort of corruption on the system that a) corrupted your database - as we had to go back to a previous version, and b) corrupted parts of your system.

A Windows reinstall will fix that.

Please let us know,

Jeff

Fantastic! Thanks for updating us Chuck.

Jeff