I'm sorry for misunderstanding your question. After some experimentation this morning, I've concluded that the size of a column in a PV window is dependent on the field size of the column of data passed into the PVRec.
So I took one of our custom PVRec's and altered the data field size in an underlying view. (That way I didn't actually have to change the PVRec to test).
In my example, I took the field length of ItemxRef.AlternateID from 30 to 20, and updated the formatting on the Inventory ID field to include dashes for each segment. After altering just the view that fed the data into the PV lookup window, the column sizes did change. My formatting on the Inventory ID showed up as well - my inventory ID now has dashes.
Sample code follows.
My assumption is that if your Stored Proc & related PVRec were to designate the field size in the query, then the column size would reflect that field size in the column width of the PV.
Hope this helps.
Gail J-N
SELECT
TOP (100) PERCENT left(AlternateID,20) as AlternateID, dbo.ItemXRef.AltIDType, dbo.ItemXRef.EntityID,
Case when len(dbo.ItemXRef.InvtID) > 7
then left(dbo.ItemXRef.InvtID,7)+'-'+ substring(dbo.ItemXRef.InvtID,8,3)+'-'+substring(dbo.ItemXRef.InvtID,11,4) +
'-'+ substring(dbo.ItemXRef.InvtID,15,6)
else dbo.ItemXRef.InvtID End as InvtID,
dbo.ItemXRef.Descr
FROM dbo.Inventory
INNER loop JOIN dbo.ItemXRef WITH (nolock) ON dbo.ItemXRef.InvtID = dbo.Inventory.InvtID and (dbo.Inventory.TranStatusCode IN ('AC', 'NP'))
and AltIDType not in ('V')