Hey there Dave. Just a thought here...
Since the MDB was touched by two different versions of Access (which may have
performed a Brundle-Fly maneuver on it), what I would try is this:
1. Make note of any steps you can do that are known to produce the error.
You'll need these in final testing af
Hi,
I have an Access DB that was created in MS Access 2003. It has several tables
in it. Then the DB was opened in MS Access 2002 and 3 tables were added to it.
When I run my CF code on my local machine (MX 7, Access Driver version 4.0) I
have no problem running my queries. When I run my CF
Thanks,
That did it. I was using the normal CF_SQL_VARCHAR
Matt Robertson wrote:
>Sure it works fine.
>
>You must use cf_sql_longvarchar as the cfsqltype. cf_sql_clob might
>work as well but cf_sql_longvarchar cfsqltype is a gaurantee.
>
>
>
Sure it works fine.
You must use cf_sql_longvarchar as the cfsqltype. cf_sql_clob might
work as well but cf_sql_longvarchar cfsqltype is a gaurantee.
--
--mattRobertson--
Janitor, MSB Web Systems
mysecretbase.com
~|
Find out h
Does anyone use an Acess DB with a table that contains
a field type of MEMO?
If so, can you check to see if any data contained there
has more than 255 characters?
Everytime I attempt to enter 300+ characters into the
field I get the error:
invalid precision error
The field type is in fact a MEM
That times out on me, could someone see if it does on thier machine also.
Robert Everland III
Dixon Ticonderoga
~~
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
6 matches
Mail list logo