VARCHAR in table, CHAR in view

So, I'm working on a system right now that has a requirement that the character columns in our tables be of CHAR data type. This is due to an interface with some legacy application and is not negotiable. My question is this- If I created a view against the table where the only difference was that the table used VARCHAR and the view used CHAR, would there be any kind of performance hit using the view? There wouldn't be any filtering or joining in the view, just a one-to-one mapping of tables to views with the data type conversion. Are there any internal issues I should know about before trying this? -- --Marty Allred Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.