memo/blob field

[Jillp]

I have checked out all the questions and answers available for this subject and still don't find a solution that will help me. Maybe someone has some thoughts on the following problem:

When using Winnt 4.0 with Crystal 8.0 I have often used the SQL statement work around, typing in a blob field and defining its length, then going on to use it in formulas etc.

When I open these same reports in a W2K machine I receive an error message; 'invalid field found here'.

We are running a Progress Database and my MRP provider had a white sheet describing how to change the length of these fields as an alternate work around but still we are receiving 'invalid field found here'.

In a couple of Answers I saw someone mention 'create a view'. I'm not sure what that means, is it something that I could try?

Any help would be appreciated,

Thanks, Jill

 

[paulmarr]

Hi Jill,

The easiest answer is to upgrade to Crystal 9 or above:

Increased limits
Formulas can now work with memo fields, and they can now process strings up to 64K in length, as opposed to a string-size limit of 255 bytes in previous versions.

Because you are limited to 255 characters - anything more is a memo field - you cannot write formulas, etc - infact the only thing you can do with it is display it.

Another answer is to modify the database if possible - breaking up the memo field into 2+ fields of 255 chars (string) - and then in the report concatinate the fields together to reform the Memo field.

A view is created within the database - which can be a table with only fields you wish to view - to a concatenated "table" which is really many tables joined together. I dont know whether you can break a memo field down in a view - perhaps another tipster could help you out here!

hope this helps

paulmarr

 

[Jillp]

Thanks for your reply, I'll probably upgrade to 9.0 to resolve this issue.

Thanks Again,

Jill

 

[synapsevampire]

I've never heard of that error, are you paraphrasing?

A search of google nets zero results for that phrase, so that's very unusual. If you aren't stating the actual error, please do so.

Does the W2K machine have a different Progress driver installed?

This doesn't sound like a Crystal error, rather a database error. Perhaps it's the way the substring is being passed to the driver on the W2K machinces, hence my guess that it's a different connectivity.

A View is basically a SQL Statement stored on the server yet it's treated similarly to a table, check with your dba:

http://webapp.progress.com:6336/dyn...ric__BookTextView/12371;cs=default;ts=default

-k

 

[Jillp]

'invalid field found here'
is the exact phrase I am receiving.

We connect through odbc in exactly the same way as the NT machines and we use only one version of progress.

As far as a dba, I am as close as it gets so I must be out of luck!

Thanks for your response.

Jill

 

[rosemaryl]

Dear Jillp,

Hmm, what is different about NT4 from W2K?

Are you absolutely positive that the drivers used for database connections on the two os's are exactly the same?

I have received that exact same error before on SQL Expressions and can track it to the difference in ODBC drivers between two different backends.

Can you post your actual expression? We might be able to change the syntax to work in both.

For example, are you using the function from Crystal's SQL functions or direct sql? (does the function start with {fn Substring(Field,Position,[length])} or do you do it directly like (Subsring(Field,Position,[legnth]).

Length is in brackets to indicate it is optional.

Hope this helps,

ro

Rosemary Lieberman
rosemary@microflo.com,

http://www.microflo.com

Microflo provides expert consulting on MagicTSD and Crystal Reports.

 

[rosemaryl]

Dear Jillp,

Sorry for the typos in that, hit submit when I meant edit!

That last bit should read:

Does the function start with:

{fn Substring(Field,Position,[length])}

Or, do you do it directly like:

Subsring(Field,Position,[legnth])

or, are you doing something totally different?

Length is in brackets to indicate it is optional.


Rosemary Lieberman
rosemary@microflo.com,

http://www.microflo.com

Microflo provides expert consulting on MagicTSD and Crystal Reports.

 

[Reebo99]

This same error message was quoted in the following thread :

thread767-724386



Reebo
UK

Please Note - Due to current economic forcast and budget constraints, the light at the end of the tunnel has been switched off. Thank you for your cooperation.