Need long text field is Access with SQL backend

  • Thread starter Thread starter Robert Harrison
  • Start date Start date
R

Robert Harrison

I'm frustrated on this one.

I need to have a field that can hold a large amount of text data. The
back-end is SQL server. I've tried various data-types, but I either can't
type more than 256 characters into the field OR if I can, then the field
can't be edited. What do I need to have set up to accomplish this?

If I get that part working. Is there anyway to use RichText in an access
textbox?

Thanks for any help.
 
I need to have a field that can hold a large amount of text data. The
back-end is SQL server.
Click to expand...

In Access it's a memo field; SQL server calls it a TEXT field.
If I get that part working. Is there anyway to use RichText in an
access textbox?
Click to expand...
Not natively, but there are RTF-aware Active-X controls on the market that
work in Access.

HTH


Tim F
 
Still having the same problem. I created a SQL table with three fields:
ID, primary key,
description (text field),
and timestamp.

When I link to the table in access I can enter into the description field as
many characters as I want. All of the data in the SQL table is correct.
However, if I go back to a previous record, it shows #deleted in the forms
textbox, except for the first record which does show properly.

But if I try to edit the description field on the first record, I get the
error that another user has modified the record and I can't change it. All
I can do is copy changes to the clipboard or delete changes.

Any ideas?

Bob

PS: I'll worry about rich text later once I get this fixed.
 
This can happen if you modified the back-end table after you linked it in
access.
Make sure ID is of Integer data type and Identity and Primary Key properties
is set, then delete the linked table from Access
and link it again. Using Linked table manager to simply relink the table may
not work, and if you previously selected "Save password" option, it will be
lost.
That should fix the problem with #deleted.

Alex.
 
I had the primary key set to bigint. That was the problem. Thanks so much.
Seems to be working correctly now. Now I'll tackle the Rich Text. It looks
pretty easy with the example at Microsoft.

Bob
 
The PK probably is some sort of Decimal type.
Access can get "confused" when trying to exactly identify two decimal values
and so it thinks someone else edited the record when in fact the comparison
is off infinitesimally.

Change the PK to Integer.
 
Back
Top