Hi all,

I'm beating my head against the monitor on this one, gang.

I have a generic "lookup maintenance" form I use in several apps where VFP is the back end. I create an updateable view called vwLookup in the DBC, and put the following code in the OpenTables() method of the form's DataEnvironment:
(NOTE: these apps all use Visual MaxFrame Professional as the framework)

*== frmLookup.DataEnvironment.OpenTables()
LOCAL lcDbc, ;
	llOpenOK

*-- Set the desired VFP parameters
THISFORM.PrivateDataSessionSets()

*-- Define local variables
lcDbc = oApp.GetAppInfo( "ActiveDBC" )

WITH oMeta
	*-- Open the database
	.oSdtMgr.OpenData( lcDbc, ;
		        .t., ;
			.f., ;
			, ;
			, ;
			THISFORM.DataSessionId ;
			)

	*-- Select the desired DBC
	.SetDatabase( lcDbc )

	*-- Open the desired tables
	llOpenOK = .oSdtMgr.OpenTable( "vwLookup", ;
					, ;
					, ;
					"vwLookup", ;
					.t., ;
					THISFORM.DataSessionId ;
					)

ENDWITH && oMeta

*-- Set the InitialSelectedAlias property
THIS.InitialSelectedAlias = "vwLookup"

*== End method frmLookup.DataEnvironment.OpenTables()

For some reason, on the app I've just created, SDT can't find the view on the OpenTable() command and creates an error dialog with "vwLookup is not a valid object name". I've opened the view through the DBC without trouble, checked the name (it's okay), and this exact code works perfectly in all the other apps. I've even re-created the DBC from scratch -- no dice.

FWIW, SDT instantiates beautifully and opens the DBC without a hitch with the correct name and location. I'm using SDT 5.1e (the version this client owns, and probably won't upgrade). I also have two extended properties on this view, and SDT can't see those either.

What senior moment/Twilight Zone have I gotten myself into this time? (G)

TIA.