Skip to main content

Posts

Showing posts from 2010

Upgrading the Scribe NAS adapter from 1.3 to 1.5

The 1.5 version of the adapter is not 64 bit compatible and uses the more stable NAS to read and write to NAV. I ran across this yesterday, with scribe support we upgraded one of the NAS's to 1.5 (upgraded to 1.4 first) and it works fine.  However, the help file for 1.5 only states to move these files: Scribe.NavAdapter.NasHook.dll Scribe.NavAdapter.NasHook.tlb Scribe.NavAdapter.NasHook.XmlSerializers.dll ScribeNasSettings.xml Scribe.MSXML4.dll \ScribeModifications \ReleaseNotes However, the additional NAS's will fail when attempting to connect to them in the workbench.  You also need to copy these files, which were installed in the 1.4 upgrade.  I suspect since the 1.5  adapter  no longer uses C/Side that these libraries need to be in the  install  directory for each NAS. AuthHelper.dll Interop.AuthHelperLib.dll These files are not listed in the help file for 1.5.  This should not be an issue if you upgraded all of the NASs to 1.4.  

Referencing a formatted text source field, using the SQLQUERY function and 'LIKE'

Scribe has the ability to insert SQL queries against a source or target (which does not have to be a database for Scribe).  This works great when searching against distinct values. However, what if you need to format a source field to strip out and prefix text, then match it up to a larger field?  In SQL you can declare a variable and perform a LIKE statement. Plugging that statement into Scribe will cause it to fail.  Here is the workaround. Format the source variable, and save it as a calculated variable to call later. RIGHT( S1, LEN(S1)-SEARCH(" ",S1  ) )  = cvTrim Then call your query. SQLQUERY( cv_Trim, "T", "SELECT [TableField] FROM [Database].[dbo].[Table] WHERE [TableField] LIKE '%' + '%s' + '%' " ) %s references the source field.