Error editing schema for both new and existing ODBC feature sources

[andrewd]

Using Windows 7 x64 and having MGOS installed on Windows Server 2008 x64, I can't create any ODBC feature sources without Maestro 3.0b2 throwing an error (see attached screen cap). This happens using all of my DSNs, which are located on the Windows 2008 x64 server, and is regardless of the type of database (I get the error for Access databases and SQL databases). It should be noted that these DSNs are 32bit.

This process worked fine in Maestro v2 (and even v1, actually).

[andrewd]

screen cap of "edit schema" error

[jng]

Does it work if you click "Test Connection" first before clicking "Edit Schema"?

[andrewd]

Yes - that seems to make it work...though, as a side note, the "test connection" doesn't actually give any notification about whether the test actually failed or succeeded.

[jng]

Select the text in that connection status field and drag all the way down. The error message is being cropped out.

This is a small oversight. The textbox control doesn't have vertical scrollbars enabled when it should

I've done some tweaking of the UI layout in this editor (r5671) to make the connection status field bigger.

[andrewd]

Beta 3 fixes this - though if it were me, I'd have just added the "test connection" function to fire before "edit schema" every time...rather than force the user to "test connection" every time before editing the schema. If it's mandatory, why not just make it run automatically if it hasn't already been run?

[jng]

That message is a beta 3 stopgap measure. This will have the "test connection" logic executed before editing or resetting the configuration document.

[jng]

RC1 executes this "test connection" logic before allowing you to edit or reset the schema.