I assumed that i was having problems because I was new to vb.net and VS, and my thinking was based in FoxPro (VFP) but that appears to not be the case.

The UltraWinSchedule with Database support demo functions perfectly when used locally, but dies when you flip the internal switches to attach it to a MS SQL db.

-------------------

In frmMain.vb, change the line that says

Const DATABASE_SQLSERVER As Boolean = False

to True

-----------

in DatabaseSupport.vb, change the connection string to use your values

'Private Const DATABASE_CONNECTION_STRING_TEMPLATE As String = "Provider=SQLOLEDB.1Persist Security Info=FalseUser ID={0}Password={1}Initial Catalog={2}Data Source={3}Use Procedure for Prepare=1Auto Translate=TruePacket Size=4096Workstation ID={4}Use Encryption for Data=FalseTag with column collation when possible=False"

-----------

Then run the program, and it will either crash with an internal exception that the connection string is too long, or if the connection string is good, the program will crash the first time it attempts to read the owners table.

I have repeatedly been able to prove that if I stop program execution before it encounters this line in frmMain.vb/InitializeUI,

' Add a checkbox for each owner in the collection to the Panel control

Me.InitializeOwnersPanel(False)

If I stop before this line and step thru the code line by line, it will function as written.  If I hit this section full-speed, it will terminate without an exception.  I can insert a wait loop for any amount of time before this code, and it matters naught:  the program will only perform as written if i step thru it line by line until after the first access to the owners table - then it can resume full speed without problems.

Hasn't anybody ever run this code as written?  I've been waiting 2 days on a support ticket with no word, thought I'd see if any forum readers know anything about this.