I have a 2-field table I want to trim strings off of one of the fields...

[MLH]

My table has an autonumber field and a text field named
[RawData]. Many records have unnecessary spaces padding
the front and end of [RawData] - at least, I think they're spaces.
The look like spaces to me.

Here's the SQL I'm using...
UPDATE Addresses SET Addresses.RawData = Trim$([RawData]);

"Microsoft Access didn't update 2353 field(s) due to a type conversion
filter..." I wonder what kind of type conversion Access is trying to
do on a text field string with text in it?

[MLH]

"Microsoft Access didn't update 2353 field(s)
due to a type conversion failure..."

Above is how the error msg read - type conversion failure
NOT type conversion filter.

[Terry Kreft]

Try the following query
SELECT ASC(LEFT(RawData, 1)) FROM Addresses

If you get 32 then they are spaces if you don't then that may be the cause
of your problem.

Also try using Trim rather than Trim$.

Terry Kreft


"MLH" <CR**@NorthState.net> wrote in message
news:ig********************************@4ax.com...

My table has an autonumber field and a text field named
[RawData]. Many records have unnecessary spaces padding
the front and end of [RawData] - at least, I think they're spaces.
The look like spaces to me.

Here's the SQL I'm using...
UPDATE Addresses SET Addresses.RawData = Trim$([RawData]);

"Microsoft Access didn't update 2353 field(s) due to a type conversion
filter..." I wonder what kind of type conversion Access is trying to
do on a text field string with text in it?

[MLH]

Thx, Terry. I don't know what happened. I must have
had some corruption in the table. I created the table
in a new database, exported the text to file, imported
the records into the new table and new dbase AND
the same query. Everything ran perfectly. I did notice
that a very few records did not make it from dbase 1
to dbase 2. That was no biggie. I entered them
manually. Must have been corruption. Dunno.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxx

Try the following query
SELECT ASC(LEFT(RawData, 1)) FROM Addresses

If you get 32 then they are spaces if you don't then that may be the cause
of your problem.

Also try using Trim rather than Trim$.

Terry Kreft


"MLH" <CR**@NorthState.net> wrote in message
news:ig********************************@4ax.com.. .

My table has an autonumber field and a text field named
[RawData]. Many records have unnecessary spaces padding
the front and end of [RawData] - at least, I think they're spaces.
The look like spaces to me.

Here's the SQL I'm using...
UPDATE Addresses SET Addresses.RawData = Trim$([RawData]);

"Microsoft Access didn't update 2353 field(s) due to a type conversion
filter..." I wonder what kind of type conversion Access is trying to
do on a text field string with text in it?

[Terry Kreft]

So long as you found it, that's the main thing.

I've been chasing a bug all morning which turned out to be due to two
factors interacting with each other, depending upon run conditions and I
only found the answers by a couple of lucky guesses, so heres to the fragile
wall I bang my head against <g>.

Terry Kreft
"MLH" <CR**@NorthState.net> wrote in message
news:qc********************************@4ax.com...

Thx, Terry. I don't know what happened. I must have
had some corruption in the table. I created the table
in a new database, exported the text to file, imported
the records into the new table and new dbase AND
the same query. Everything ran perfectly. I did notice
that a very few records did not make it from dbase 1
to dbase 2. That was no biggie. I entered them
manually. Must have been corruption. Dunno.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxx

Try the following query
SELECT ASC(LEFT(RawData, 1)) FROM Addresses

If you get 32 then they are spaces if you don't then that may be the cause
of your problem.

Also try using Trim rather than Trim$.

Terry Kreft


"MLH" <CR**@NorthState.net> wrote in message
news:ig********************************@4ax.com. ..

My table has an autonumber field and a text field named
[RawData]. Many records have unnecessary spaces padding
the front and end of [RawData] - at least, I think they're spaces.
The look like spaces to me.

Here's the SQL I'm using...
UPDATE Addresses SET Addresses.RawData = Trim$([RawData]);

"Microsoft Access didn't update 2353 field(s) due to a type conversion
filter..." I wonder what kind of type conversion Access is trying to
do on a text field string with text in it?