Would you believe varchar(max)

[jaydwest]

I created some fields in SQL Server 2005 with a new datatype varchar(MAX). Then I linked the table to MS Access 2003. But the SQL Server boys did not talk to the MS Access boys. Access mapped the field to a text field with 255 chars and not a memo field. When the content of the field in SQL Server exceeds 255, Access does not allow the record to be updated.

Am I smoking some strange weed, or has anyone else found this problem too?

 

[SQL_Hell]

If you use access project (.adp) you wont have this problem

 

[Mad_Philly]

If you use access project (.adp) you wont have this problem

What???

Jay I'm just finding this problem now and have posted in the Forms forum. Hopefully there's a solution for it as it's insanely annoying!!!!

 

[jaydwest]

Hi mad,

It's been a while since I posted this. What I have resolved to do is not use varchar(max). Would have been nice but that's the way it goes with MS. I still use varchar(800) to varchar(1800) or so for memo fields. So far no clients have called in to complain that they don't have enough space.

Good Luck,

 

[Mad_Philly]

Problem I have is that some of the strings in this field are up to 4000 characters :S

Fingers crossed there's something I can do without faffing around!