WynApse

Here's a great idea, and it's free: blogmailr. You get yourself signed up, want to add to your blog, send an email to an @blogmailr.com address... how cool is that?

Thought I'd mention that they don't work with .text yet (e.g. geekswithblogs), but they said it would probably be just a couple days. I'll mention it here when I hear back from them.

Meanwhile, you can get an acct and setup email addresses you will write from :)

I'm not convinced that the Crystal Reports "Exception" is a real deal in my case because of two conflicting scenarios

1. I restored from Version Control, pulled out all but two of the existing fields in the xsd element I wanted to replace. I modified the query to pull from a different table. I added one field of the two I need into the element, and when I added the 2nd one, I got the exception. I could not make the exception go away by backing off the work I'd done.
2. I restored from Version Control, pulled out all but two of the existing fields in the xsd element I wanted to replace, and got the exeption right then.

Either I get the exception uniformly or something else is in play.

I always tell young developers "If it didn't do this earlier today, and it doesn't make sense, reboot". So I tried. When the PC came back up, it came back up strange and had to be hard booted again, so I'm wondering if I've had a resource problem all along. We'll see in the morning.

This one is a grand example of why I have such warm and fuzzies about Crystal Reports:

Reference Part II from yesterday.

It is 2:58 on Tuesday. I've been dorking with this since Friday afternoon sometime. About 1/2 hour ago I pulled everything back in from Version Control for about the 4th time today.

I modified the existing subreport by pulling fields out of the element associated with the report, and miraculously got it to accept it.

I then went into the code behind and pulled the data from the REAL table, and that worked!

So what I had was data from the table I wanted it from, populated to a subreport with 2 of 4 fields showing.

I modified the xsd file again and added just one of the two remaining fields, but I could not get the Field Explorer to change.

I deleted the .cs for the .rpt file and shut down Visual Studio and restarted it. Since I (obviously) have no idea what makes this work or not, I did a rebuild all. I then went into the Field Explorer and lo and behold, it has changed!

It changed back to what it was 1/2 hour ago! .... sigh...