I am sitting here with both my Crystal 8.5 and my SQL guides out and still can not find the answers I am looking for...
I know that if I want to block an item that starts with a certain phrase I can use the code
Code:
------------------------
not({item.itm_desc} startswith ["cement","interpore","collagraft","mesh"])
------------------------
... however, my problem is that the items that I want to block do not START the description... the words are within the description - just not at the beginning of it . I know it is still possible to block items based on those words, but I can not remember how to code the report to do so...
Also - just to make life a little more interesting - there is 1 item that begins with the word "mesh" that i DO want to show up on this report. is there coding that says something to the effect of "ignore all items beginning with "mesh" EXCEPT item # 54446" ?
Does anyone have any ideas? Any suggestions would be greatly appreciated...i just wanted to let yall know someone gave me the following suggestion in regard to the second question and it worked great:
Code:
------------------------
If {Item_no}="54446" then {item.itm_desc}={item.itm_desc} elsenot({item.itm_desc}startswith "mesh")
------------------------
i am still searching for the first answer, but at least the second one has been put to rest...
thanks
Showing posts with label items. Show all posts
Showing posts with label items. Show all posts
Sunday, March 11, 2012
Saturday, February 25, 2012
blob size limit
is there a size at which the items just get too big to be practically stored
in blobs?"jason" <jason@.discussions.microsoft.com> wrote in message
news:21C19525-825F-4DD3-83E6-B257AB500946@.microsoft.com...
> is there a size at which the items just get too big to be practically
> stored
> in blobs?
Not really, but you have to be increasingly careful with blobs as they get
bigger. For instance in client applciations if you can't afford to easilly
store the whole blob in memory, you need to use streaming access to move it
into and out of the database.
David|||Hi Jason,
In SQL 2000 ntext, text, and image data types are capable of holding
extremely large amounts of data (up to 2 GB) in a single value. In SQL
2005, varchar(max), nvarchar(max), varbinary(max) and nvarbinary(max) also
has 2 GB limitation.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
in blobs?"jason" <jason@.discussions.microsoft.com> wrote in message
news:21C19525-825F-4DD3-83E6-B257AB500946@.microsoft.com...
> is there a size at which the items just get too big to be practically
> stored
> in blobs?
Not really, but you have to be increasingly careful with blobs as they get
bigger. For instance in client applciations if you can't afford to easilly
store the whole blob in memory, you need to use streaming access to move it
into and out of the database.
David|||Hi Jason,
In SQL 2000 ntext, text, and image data types are capable of holding
extremely large amounts of data (up to 2 GB) in a single value. In SQL
2005, varchar(max), nvarchar(max), varbinary(max) and nvarbinary(max) also
has 2 GB limitation.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)