This is a response to the question about including HTML in Event descriptions here: http://www.imiscommunity.com/complete_newbie_need_help   I'm posting it here so I can attach a screenshot.

Something else that might help...

The Event Directions field, from Define an Event in Desktop, is rendered as an asp:Label in public view and template sites, so it can include HTML formatting for bold and hyperlinks.  The attached screenshot shows the desktop setup, with html in the Directions field, and its effect in public view.  I didn't check to see how confirmation notices would handle HTML, so you'd probably want to check "Suppress printing of directions on Confirmation Letters".

Up through SQL Server 7.0, to determine the level of SQL Server, the routine was to execute SELECT @@VERSION, note the version number, and look it up in the table on the Microsoft site -- http://support.microsoft.com/kb/321185 .

With SQL Server 2000, SELECT SERVERPROPERTY ('ProductLevel') was introduced, which returns "RTM", "SPn", or "Bn", for Release to Manufacturing, Service Pack n, or Beta n.

This is a non-iMIS problem I wanted to solve for my photography hobby, but there may be some interest in how to use LINQ to work with EXIF data from image files.

In this case, I had photos from two different camera bodies and the same event, and wanted to post them to a photo site, ordered by the date/time they were taken.  Unfortunately, the site didn't support sort by date taken, just by file date modified.  Since the photo ID numbers for the cameras weren't in sync, I couldn't use them for the sort.  I'd started with .NEF format image files, and generated .JPEGs from them, so the order of the file date modified didn't necessarily match up with the date taken.

I've seen numerous questions about the inability to use sp_who with iMIS 15 to see who's logged in.  iMIS 15 uses the equivalent of the 10.x SQL security model 3 (only), so there's not a SQL-login-per-user model available, which lent itself so nicely to using sp_who.  The reason for this is the iMIS 15 adoption of the ASP.NET Membership Provider as a single unified authentication store and the need to integrate it throughout iMIS, including the Desktop environment.

The Paypal test account is limited to transactions less than $1000.  If you try to authorize a larger charge, Paypal / PayflowPro will return a DECLINED status, so you can confirm that declined transaction handling is working properly.

The session handout and the samples from this session, presented on April 28, 2009, are here: http://www.imiscommunity.com/implementing_payment_gateways_innovations_2...

I ran into this when installing Acrobat Reader on a Vista system where User Account Control was turned off. To get past the error, turn UAC back on (Control Panel / User accounts).

More details from Adobe: http://kb2.adobe.com/cps/333/333643.html

The handout from the Innovations 2009 SSRS presentation is attached.

Here, just in time for Innovations, is an animated cursor based on the ASI logo. To install it, copy the asi_pinwheel.ani.txt file to your windows\cursors folder. Take off the .txt extension. In Control Panel / Mouse / Pointers, Browse to this cursor for the "Busy" and "Working in Background" selections. Click Apply and you're done.

If you encounter this error, the very first thing to check is whether you can login to the full web view. Desktop uses the Membership Web Service for authentication, and the service runs as part of the iMIS 15 install on the application server (the URL specified by key="ImisWebServerUrl" in web.config). If you can't login to the full web view, try restarting IIS. If that doesn't fix the problem, the iMIS 15 server installation needs additional troubleshooting.