VI Server Properties & Methods that are unavailable
when using the LabVIEW 5.1 App Builder

(Note the lists below apply ONLY to version 5.1. According to the dialog below, the list was much longer for previous versions.)

The following was excerpted from an email exchange between Dan Bookwalter [bookwald at histat.com] and an unnamed Senior Software Group Manager at NI.

> I have just been told by one of the NI Tech guys that if I use the VI Server in any of
> my applications I cannot build the app into a standalone executable.... Is this true???

No this is not true. You are able to build the app into a standalone executable. However, it is possible that some of the properties and methods on VIs and the Application will not work (but will return errors) in a built app. Some of the features exposed through the VI Server are only available in the Full Development System and not in the run-time system.

These features are not available in the run-time system of LabVIEW because they are of a development nature, or they modify a VI beyond what can be done in the run-time system. We re-evaluated many of them for 5.1 and made more of them available in the run-time system. It is possible that there are still some that can be made available in the run-time system. One popular request is the VI method: Make Current Values Default. This may change although there are issues regarding the integrity of a call to a VI if you invoke this method while the call is in progress.

VI Properties that, when set, will fail with an error in an app built in LabVIEW 5.1:

Description
History
AllowDebugging
ExecShowFPOnLoad
ExecRunWhenOpened
ExecIsReentrant
SuspendOnCall
ExecPriority
Name
BDWinOpen
BDWinBounds
HistUseDefaults
HistAlwaysAddAtSave
HistPromptAtClose
HistPromptAtSave
HistRecordLVComments

VI Properties that, when read, will fail with an error in an app built in LabVIEW 5.1:

History
HistUseDefaults
HistAlwaysAddAtSave
HistPromptAtClose
HistPromptAtSave
HistRecordLVComments
UserChanges
BDMods
BDWinOpen
BDWinBounds

VI Methods that will fail with an error in an app built in LabVIEW 5.1:

ExportText
SaveInstrument
Revert
PrintDocsToHTML
PrintDocsToRTF
PrintDocsToTextFile
PrintDocsToPrinter
SetLockState
MakeCurValDefault

App Properties that, when set, will fail with an error in an app built in LabVIEW 5.1:

PrTextWrap
PrPNGCmp
PrJPGQual
PrCustConn
PrCustDesc
PrCustPnl
PrCustPnlBrdr
PrCustCtl
PrCustCtlDesc
PrCustCtlType
PrCustDiag
PrCustDiagHidd
PrCustDiagRepeat
PrCustSubVIs
PrCustHier
PrCustHist
MenuSet
PrCustAllCtls
CtrlPalOpen
FuncPalOpen
ToolsPalOpen
UserName

App Properties that, when read, will fail with an error in an app built in LabVIEW 5.1:

PrTextWrap
PrPNGCmp
PrJPGQual
PrCustConn
PrCustDesc
PrCustPnl
PrCustPnlBrdr
PrCustCtl
PrCustCtlDesc
PrCustCtlType
PrCustDiag
PrCustDiagHidd
PrCustDiagRepeat
PrCustSubVIs
PrCustHier
PrCustHist
MenuSet
PrCustAllCtls
CtrlPalOpen
FuncPalOpen
ToolsPalOpen

Most App Methods are NOT available in a built app in LabVIEW 5.1, so this is a list of the ones that ARE available:

BringToFront
DisconnectSlave (used by Host LabVIEW RT)