I think you ran into the phenomenon where sql server doesn't update the metadata of a view with updated metadata of the underlying tables until the view is dropped/recreated.
E.g. if you do in a view:
select * from customers
and then alter the customers table to change some length of a field in customers, the view metadata might not get updated. LLBLGen Pro pulls the metadata from the system views, but this thus can be outdated.
So if you go into SSMS, simply open the view in create script. Then drop it, then recreated it and then in llblgen pro sync with the catalog which should pull the right metadata into the project.
We use the following query:
SELECT INFORMATION_SCHEMA.COLUMNS.*,
(SELECT COLUMNPROPERTY(OBJECT_ID(@sFullTableName),
INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'IsComputed')) AS IsComputed,
(SELECT COLUMNPROPERTY(OBJECT_ID(@sFullTableName),
INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'IsIdentity')) AS IsIdentity,
(SELECT COLUMNPROPERTY(OBJECT_ID(@sFullTableName),
INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'IsRowGuidCol')) AS IsRowGuidColumn,
(SELECT COLUMNPROPERTY(OBJECT_ID('@sFullTableName'),
INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'GeneratedAlwaysType')) AS GeneratedAlwaysType
FROM INFORMATION_SCHEMA.COLUMNS
WHERE INFORMATION_SCHEMA.COLUMNS.TABLE_NAME='<your table>'
AND INFORMATION_SCHEMA.COLUMNS.TABLE_SCHEMA='<your schema>' ORDER BY INFORMATION_SCHEMA.COLUMNS.ORDINAL_POSITION ASC
(replace <your table> with the name of the view, <your schema> with the name of the schema (e.g. dbo) and @sFullTableName with the string [schema].[view] (or remove these fields from the query , as views don't need those)
This should give you the info the designer sees as well, which might give you an idea where the problem is...