Re: MS Query Problem
- From: "Me!" <dummy@xxxxxxxxxxx>
- Date: Tue, 30 Jun 2009 15:15:14 +0100
Hi Dave,
The field is a 20 character text string which represents an industry code,
with each character representing a particular 'aspect' of a car, i.e.
manufacturer, engine size, number of doors etc. and when the code was
originally designed a space was used as a null for each character field if
any aspect as null, rather than a non-standard character. And as it is an
industry standard code and embedded in 1000s of companies own systems a
retrogade changing of all codes to handle the spaces differently isn't
feasible.
So I'm left to try deal with it. SQL Server deals with it fine, it's just
access & excel that are a problem.
Cheers..........Jay
"Klatuu" <Klatuu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:92F7CD87-063A-4FD2-9EA0-E64DC5A1A68F@xxxxxxxxxxxxxxxx
No, it can't be avoided directly. The database engine is dropping the
trailing spaces.
It would be a very unusual circumstance to keep trailing spaces. The only
solution would be to keep track of the desired length of the field and add
the spaces back to it, but I can't think of a reason to do so.
--
Dave Hargis, Microsoft Access MVP
"Me!" wrote:
Hi,
I'm using MS Query to execute a stored procedure in an Access .adp
sqlserver
link and return the data to Excel.
It works fine, but when the result set is returned to Excel, any fields
with
trailing spaces have the trailing spaces truncated.
Does anyone know why this happens and if it can be avoided?
Many thanks......Jason
.
- Follow-Ups:
- Re: MS Query Problem
- From: Klatuu
- Re: MS Query Problem
- References:
- MS Query Problem
- From: Me!
- RE: MS Query Problem
- From: Klatuu
- MS Query Problem
- Prev by Date: Date Criteria not working...
- Next by Date: RE: Date Criteria not working...
- Previous by thread: RE: MS Query Problem
- Next by thread: Re: MS Query Problem
- Index(es):
Relevant Pages
|