Micro_soft Access. How do I work with fields longer than 255 characters?

[Antonio]

see title

Is there a better alternative? I'm trying to sort out some galleries' urls and descriptions and if the url is longer than 255 characters it gets fucked up.

any help, advice, etc. is appreciated ;)

[arg]

Two approaches to consider:

1. Use multiple text fields, each 255 characters, like description1, description2, and description3 which you concatinate together for output. If you're just importing them through text files, coding the import to split them into 255-character chunks is reasonably easy. However, if you want edit them from an Access form, it would be a hassle. (Possible with VB, but a hassle).

2. Use a memo field instead a text field. The drawback with this is you can't perform certain operations on a memo field as easily (e.g. string operations like capitalizing letters or appending another string to it). If you're just inputting, editing and reporting the field, that's no problem, but if you do need to perform string operations on it, you need to do some conversions in VB with more complicated library calls.

[Antonio]

Originally Posted by arg

Two approaches to consider:

1. Use multiple text fields, each 255 characters, like description1, description2, and description3 which you concatinate together for output. If you're just importing them through text files, coding the import to split them into 255-character chunks is reasonably easy. However, if you want edit them from an Access form, it would be a hassle. (Possible with VB, but a hassle).

2. Use a memo field instead a text field. The drawback with this is you can't perform certain operations on a memo field as easily (e.g. string operations like capitalizing letters or appending another string to it). If you're just inputting, editing and reporting the field, that's no problem, but if you do need to perform string operations on it, you need to do some conversions in VB with more complicated library calls.

Thanks arg. The first approach seems the better alternative. I'll try it in sec ....

[Antonio]

It works like a charm



thanks again ;)

[arg]

No problem...you might still hit a snag when you try to output them as a continuous string, but there are ways of doing it, nothing too hard.

[Antonio]

Originally Posted by arg

No problem...you might still hit a snag when you try to output them as a continuous string, but there are ways of doing it, nothing too hard.

that's not going to be a problem at all
I can easily do that by pasting the whole table from Acces to a new doc in NoteTab light, and after simple replacement the two fields are joined togother ;)

[Webby]

Antonio:

hat's not going to be a problem at all
I can easily do that by pasting the whole table from Acces to a new doc in NoteTab light, and after simple replacement the two fields are joined togother ;)

It depends what you are going to do with it after it's in NoteTab - but you may want to consider getting the pro version of this and stuffing all your data into Notetab outlines. You can then use their clip programming to do loads of good stuff :-)

[Antonio]

Originally Posted by Webby

Antonio:



It depends what you are going to do with it after it's in NoteTab - but you may want to consider getting the pro version of this and stuffing all your data into Notetab outlines. You can then use their clip programming to do loads of good stuff :-)

I've been using NoteTab light for years and I love it, but I use it only for simple operations. I'm sure that with NoteTab you can do one gazzilion things but I'll never find the time to learn what all the libraries can do for me.....

I believe that everybody should have at least the Light version, it will save you soooo much time ;)