the 255 character limit per field

[Ron O'Brien]

Hi

I'm a total newbie to this seemingly complicated Access database malarky.

I am trying to build a database that will also eventually appear on my
website (hence Access being used). I produce a news letter of sorts and want
to be able to index the various articles so I get the following fields:
Date, Title, writer, Subject matter and content.

The content field being the actual article, which could be up to 300 words -
considerablyy more than the max field size of 255 characters! Is there any
logical way around this? or am I going about it in an illogical manner

Any suggestions greatly appreciated


Ron

 

[Ken Snell \(MVP\)]

A memo data type allows over 65,000 characters. Change the data type from
Text to Memo.

 

[KARL DEWEY]

Use a memo field for content.

 

[Ron O'Brien]

Thanks guys
easy when you know how eh?

BTW is there any where printed an explanation of terms used in Access? I am
sure I can't be alone in wondering what a query is or what constitutes a
query by definition together with ID's, Key's and God's knows what I've yet
to discover!


Ron

 

[Ken Snell \(MVP\)]

Any good book on ACCESS will do this... Help also provides pretty good
information for this.

 

[Klatuu]

Use a memo field instead of a text field.

 

[Jeff Boyce]

Ron

In addition to the notion of embedding your description in a memo field, you
might also consider keeping your description/text in its original form
(e.g., text file, Word document, etc.) and linking to that for display
purposes.

Or were you considering searching the description?

Regards

Jeff Boyce
<Office/Access MVP>

 

[John Vinson]

Thanks guys
easy when you know how eh?

BTW is there any where printed an explanation of terms used in Access? I am
sure I can't be alone in wondering what a query is or what constitutes a
query by definition together with ID's, Key's and God's knows what I've yet
to discover!

Lots of good books and resources on the (rather complex!) subject out
there. Check out the innumerable links at

http://home.bendbroadband.com/conradsystems/accessjunkie.html


John W. Vinson[MVP]

 

[mscertified]

Before you get too deeply into this you might also want to rethink using
Access as a back-end for a website. Its really not a good database for that
purpose and going down the wrong path could cause you to waste a lot of
valuable time over the long run.

Dorian

 

[Dirk Goldgar]

Before you get too deeply into this you might also want to rethink
using Access as a back-end for a website. Its really not a good
database for that purpose and going down the wrong path could cause
you to waste a lot of valuable time over the long run.

I agree that Ron should think about it, but I wouldn't say that Access
is an inapproprate back-end for all websites. Rather, it's not
appropriate for high-volume, high-traffic, or high-security websites.
There are thousands of websites, probably more, that use Access/Jet as
their data stores, and they run quite well. It's a matter of choosing
the right database for the job.