I am trying to define a new Access Definition that requires a View to be the parent for other tables. The view contains a CASTed column that the underlying table does not contain and is the key column needed in the relationship. I am able to define the relationship, but Optim is not acknowledging it. It currently says the relationship is in 'unknown' status, which usually implies it was deleted. However, I can open the relationship and view it.
I don't usually need to work with views, so I have not encountered this before. Has anyone else had experience with using Views as a parent in an Optim relationship and how did you make it work correctly?
Version: Optim on Windows v11.7.0.2
DBMS for the AD: SQL Server 2019
I appreciate the help from the community!
#InfoSphere Optim
-Keith Tidball
Progressive Insurance
Update on this thread: Optim Support confirmed that Optim relationships in a view only work if the column in the view also exists in a base table. So computed columns won't work. Serious shortcoming of the relationship functionality, IMO.
-Keith