Field missing in query results??

[jagilman]

I am using Access as the front end for SQL Server 7. I use a stored procedure to return a recordset. However, one field is missing from the results. It is a varchar field. About 1 month ago this same field was a text field and just started to remove itself from the results. The only way to get it to show up was to change it to a varchar field. I have found that the sql server driver on the client seems to be responsible for the missing field. Two different client boxes return different results, one with and one without. For some reason the code seems to ignore the missing value (it just passes over it like it's not there)
Any help is appreciated.

John

John A. Gilman
gms@uslink.net

 

[MichaelRed]

John,

Since you believe the problem originates w/ the SQL Server, hqave you posted the inquiry in that Forum?



MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over

 

[jagilman]

Any time I have refered to Access in that forum I just get refered back here.

John A. Gilman
gms@uslink.net

 

[MichaelRed]

John,

Sorry those folks aren't more accomodating.

Can you execut the query in the SQL Server environment and see if the results are the same? Perhaps presenting that to the 'other' forum will prompt them to look at it?



MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over

 

[jagilman]

Here is the situation, it looks like I may have a tough time getting info related to the first time this happened. The field was a text field and was working fine. The environment is an office with 5 users entering order informtaion into this SQL database. One day the mgr shows me this new problem, when she loads a customer onto the form the comments field is empty (this is common for about 60% of the customers). Then she types a comment and saves the field. Then she looks up the customer again and the comments are gone. I took a look on the server and the last comments are still in the table. However, when she saves the customer "without" making any changes to the comments the values are over writen with her blank field values. At this time I never checked to see if any other machine did this. I changed the field from a text field to a varchar field and it started to work. Then for some reason the field started to be over looked again about a month later. This time I found that only two of the machines were affected by the problem. After several hours of digging I found that the SQL Server dirver in the ODBC manager on these 2 machines were of a newer version,( 3x vs 2x ). I have not found any info on the microsoft site.


John A. Gilman
gms@uslink.net