Linked SQL Field being cut off

[Guest]

I have an ODBC SQL Linked table pointing to a view in a SMS Database. When I
open this linked table of BIOS inventory data the filed for serial number
isn't complete. Its dropping the last 2 digits of the field. However, if I
go into SQL directly the entire serial number is there.

Any ideas?

 

[Tom Ellison]

Dear Vincent:

This may be too simple an answer, but if you make the view of this column
wider, does that help?

Point to the line dividing this column from the next column to the right and
move upward to the row with the column headings. The mouse cursor will
change to be two arrows point inward toward a vertical line. Depress the
left mouse button (unless you have reversed them) and drag it to the right.
This will widen your view of this column, which may allow more information
to be displayed.

If so, you were never actually missing this data, you just couldn't see it.
There is a large technical difference here, even though it may not seem so.
As far as any computer functions, I believe it may certainly be that the
information is there. It is either hidden as I explained above, or it is
"formatted away". But it would be best to seek visual confirmation of this
in any case.

Now, I have never worked with SMS through ODBC, so you may also be
experiencing something with which I cannot help you. But, as some time has
passed and no one else has given it a shot, I just thought my idea might be
sufficiently significant to offer it.

Tom Ellison

 

[Guest]

No, data really isn't there. I am writing a VS C# app using the data and
when I point to the field via the Access Link table its cut off and when I
point to the Field directly in SQL its the complete Serial Number.

I have replicated this issue in Access.

 

[Tom Ellison]

Dear Vincent:

I'm sorry if my very simplistic "possible solution" was not applicable. It
is best to eliminate such possibilites first. You're obviously sufficiently
not so inexperienced as to fall for such a mis-perception.

I wish I had another suggestion, but I do not at the moment. I hesitated to
give this at first, as someone may have had a much better suggestion, but
when time passed without a response, I thought it worth the risk.

I would suggest you repost your original question. Many who might help you
may skip this post, seeing someone has "answered" it. If you post again, it
is more likely someone else will see it unanswered and tackle it. If I have
any further useless ideas, I'll post them to this thread and leave you new
thread alone.

Tom Ellison