I&#039;m wondering if anyone has encountered a bug with SQL Server 7.0 when they attempt to update a view which uses an alias. I&#039;ve created a view which has 3 fields that are aliased and 2 which aren&#039;t. whenever I try to update the view I get the following error: Microsoft OLE DB Provider for SQL Server error &#039;80004005&#039; <BR><BR>indicating that it can&#039;t update the field because I&#039;m using the wrong name. For example there is a field, in the view, which I call Legacy the underlying tables name for that field is Legacy_Asset_Class. When I attempt to update the view I use the name Legacy which throws the error. It might seem obvious for me to use the underlying name, however I&#039;ve written one function to adress 50 different views and passing the view names so it&#039;s not that simple. Has anyone encountered this and if you have how did you get around the problem?