Hi all,

I'm upgrading a print merge spec to WordMergeLite, and it's going much faster and more elegantly than my old WordMerge programming, but I've run into a snag.

I have a command button that executes the WordMerge Lite code that was included in the sample db from Inside Sesame 2006.  I've added a few custom variables, but that's it.

My problem is this -- I want to @promptforuserinput any required fields for the doc that are currently blank, but I'm not having a lot of luck inserting my code into the existing WML blocks.  Can anyone suggest an elegant way to screen my print job before kicking into the hefty WML code?

Here's my old screening code from Word Merge ...

// Validate record for all proposal information

vOKtoSave = 1

If @UserID <> "manager"
{
	// Assemble a message containing all the errors
	// Clear the OK flag if any validation fails

	if CltBill = ""
	{
		vMsg = vMsg + @NewLine() + "Net/Gross Billing Required!"
		vOKToSave = 0
	}
	if CltComRate = 0
	{
		vMsg = vMsg + @NewLine() + "ComRate Required!"
		vOKToSave = 0
	}
	if CltCt1 = ""
	{
		vMsg = vMsg + @NewLine() + "Contact Name Required!"
		vOKToSave = 0
	}
	if CltSales = ""
	{
		vMsg = vMsg + @NewLine() + "Salesperson Required!"
		vOKToSave = 0
	}
}

// If any validation failed show failures

	If vOKTOSave = 0
	{
		@MsgBox(vMsg, "", "")
	}
 

I cannot test right now, but this may be typical of what you could do for each of the critical elements:

While @IsBlank(CltBill)
CltBill = @PromptForUserInput("Net/Gross Billing Required!", )	 

     

And then there is Jabberwocky .....