There are several ways to confirm that your iMIS Desktop installation has the correct versions of ActiveX components.  The installer normally handles this, but once in a while some environmental issue interferes, leaving an older version of a component installed.

1. In iMIS Desktop, pick Help> About >System Info.
   
2. Download the AsiVersion utility from www.advsol.com/downloads - scroll down to the Diagnostic Tools folder and download AsiVersion.zip.
   
3. Add file version to Windows Explorer
   1. Right-click on the field columns header
   2. Pick "More..." from the context menu
   3. Check "File version" in the list. 
   4. By default, iMIS ActiveX files are in C:\Program Files\ASI\iMIS15\ActiveX.  Note that this checks the file version, but doesn't check the COM registered version loaded by desktop (they'll be the same, unless there's a problem).  The first two options do.
      

This is a command script I use to reset the iMIS world completely in my local development environment, making sure nothing's cached in IIS or ASP.NET.  The script stops the Publishing and Workflow services, stops IIS, deletes the files in the ASP.NET cache, starts everything back up, and recycles the application pool used by iMIS.

Copy the lines below and save them in a .cmd file.  It needs to be run as administrator. 

Here's a way to create an IQA query to list IQA queries and display their full document system path.

First, create a view to wrap the asi_PublishedDocumentPath function.  This view definition is for published documents only (status = 40), but change it if you need different results.

CREATE VIEW [dbo].[vDocumentPath] AS
 SELECT dbo.asi_PublishedDocumentPath([DocumentVersionKey]) AS 'DocumentPath', [DocumentTypeCode]
   FROM [dbo].[DocumentMain]
 WHERE [DocumentStatusCode] = 40 AND dbo.asi_PublishedDocumentPath(DocumentVersionKey) IS NOT NULL

Next, in Business Object Designer, create a business object named DocumentPath.  On the Database tab, add vDocumentPath, and both columns as properties.  Save and publish.

I'm reasonably sure this was working as I expected it to (i.e. copy a URL from the browser, paste it into a message, and it created a clickable hyperlink), but recently stopped working, such that I had to go through the extra steps of Insert / Insert Hyperlink.  Maybe an Office update changed the setting, I don't know...

Anyway, to switch it back, Tools / Options / Mail Format tab; Editor Options / Proofing / AutoCorrect options; check "Internet and network paths with hyperlinks" on the "AutoFormat As You Type" tab.  Note that the identical checkbox on the "AutoFormat" tab didn't affect this.
 

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 include a screenshot.

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...