Hi John, Are you running a unicode server? My guess is that you are, in which case it's only going to recognize nchar/nvarchar and is not going to recognize char/varchar column types.
If this is the case, and IF you really meant it when you wrote "need to be able to SEE these values" (and not modify), then what you need to do is create a SQL view on top of the table that casts the char/varchar columns to appropriate nchar/nvarchar types: CREATE VIEW ViewName AS SELECT ... CAST(CHAR1TypeColumn AS NCHAR(1)) AS OriginalColumnName, ... FROM YourTable Next, create your Remedy view on top of this new SQL view, and it should work fine. Again, to be clear, this solution is for READING the data. I'm not sure how well it would work if you attempted to modify data through the view. If this isn't clear and you are willing to provide specifics, I'd be happy to help craft the create statement for the SQL view. -charlie On Wed, Jun 11, 2014 at 10:10 AM, Mr Bodie <[email protected]> wrote: > ** > Hi folks, > > Need some help again. > > I created a view form in remedy but I notice that I does not show any of > the columns in the table that are Char(1). > > This is a major problem for us as we need to be able to see these values > > Can anyone think of why this would be? All the other columns come across > fine. ARSYSTEM is the owner so its not a permissions thing. > > Database is SQL server 2008r2 > > Thanks > > John > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
