WynApse

Follow-on to: Day I.

A new day, a new week, another attempt at this.

I've learned something about setting the database location. I know that previously I've gotten into the ADO.NET(XML) dialog box, and searched for the XML File Path using the top drop-down. On Friday, and what I'm using now, I ended up using the "Use Visual Studio Data Class" checkbox, and selected the class name. I'm not sure why one is working differently on a different day than another, but I'll go with what works right now - part of what endears Crystal Reports to me so much I guess.

I got the report all formatted up, but then began a new fight with Crystal Reports telling me:

Exception Details: CrystalDecisions.CrystalReports.Engine.LogOnException: Logon failed.

This is terribly frustrating because all I wanted to do was add a new table, format it into the original report (which I've done 3 other times) and go on, and here I am at the end of Day 2 of messing with this this non-intuitive bag attached on the side of Visual Studio.

I've refreshed everything from Version Control multiple times. Funny how it is when you get deep into debug, all of a sudden you reach a point that you decide "the heck with what I had here before, I just want it to RUN"... so I just pulled everything out that I had done which by this point wasn't much compared with the time spent just trying to format what amounts to data in a grid. Believe me, if it was simply one grid of data, it would have been done on Day I.

I pulled all the way back, and instead of adding an element, I modified the one that was there and added two string fields, and dummied up what was being populated there in my query. That was fine.

Then I formatted up my two fields in the report, and heaven help me, I switched the query to the correct table and damn if it didn't puke on it's shoes! I tried backing off a display element at a time, and the query and it didn't change, so I've now refreshed from Version Control once again.

In and amongst everything else, I've tried what I found here:

http://support.microsoft.com/kb/319264

to no avail.

So now I have the original code running the original report without failing and I'm just as happy as can be to see it actually working without throwing an exception.

Maybe tomorrow...

I Love Crystal Reports.