...from Fire Bowl Cafe in Austin.

This one is from Lotus Restaurant in St. Paul, MN.  The next time I ate there, I got "You can prosper in the field of medical research", so I disregarded it.

This is a stored proc to take an input URL with a query string and split out the URL and the individual query string parameters.  For example, if you're considering a URL like this:

http://localhost/imismain100/iMIS/ContentManagement/Template.aspx?ContentCode=SimpleEventEdit&UniformKey=72290518-44b9-428b-909d-10142b4b6b9f&PreserveStatefulBusinessContainer=true&ButtonId=ctl00_TemplateBody_WebPartManager1_gwpste_container_SimpleEventShowcase_ciSimpleEventShowcase_EventShowcase_RefreshButton&ParentPageInstanceKey=ae6cfeb2-21c7-4221-a2e1-43d5e6c5b097&WebsiteKey=d30229f1-d53b-48d7-99ae-d0ce9fea621d&TemplateType=E&DialogCacheParam=0.9562794873612177

Attached is an updated C# CCAuth template for use with the custom gateway.  It resolves the problems described here: http://www.imiscommunity.com/custom_imis_15_1_3_ocx  .

Here's how to illustrate an iMIS Community post; I'm not sure if it's noted elsewhere.

First, create your new post.  Scroll to the bottom and click "File attachments", which expands to show a file path entry field and Browse and Attach buttons.  Click Browse, find the image you want, and click Attach.  After the file is uploaded, under the Description there's a URL string in very small font.  Copy the URL, then in the editor toolbar, click the Insert/Edit image icon (next to the Anchor).  In the popup, paste in the URL, then tab out of the field; if all is well, you'll see your picture in the preview.  Click OK.

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.