Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recent content by ChopinFan

  1. ChopinFan

    Checking for Nulls

    Yes, we tried the standard method for an access data project, putting parameters in the report properties, but it didn't like it and wouldn't do what we wanted, so this was the solution we got to work. This is my whole procedure. I didn't mention earlier that it also has input parameters...
  2. ChopinFan

    Checking for Nulls

    Yes, only specific columns I would test for nulls.
  3. ChopinFan

    Checking for Nulls

    I have sprocs that execute sql statements stored as a string, i.e.: CREATE PROCEDURE dbo.SprocName AS set nocount on declare @SQL as varchar (2000) set @SQL = 'SELECT yada yada etc.' exec(@SQL) Using the above procedure, I need to be able to check for null values the query may be returning...
  4. ChopinFan

    Concatenation Issue

    Excellent. I had to add additional single quotes to use this inside the @SQL string, but it works. Set @SQL = 'SELECT Stuff(Stuff(FieldName, 5, 0, ''-''), 3, 0, ''-'') AliasName' etc Thanks!
  5. ChopinFan

    Concatenation Issue

    Well, I got around the problem by splitting the field into three pieces in the query and inserting the dashes in the application layer instead. Nevertheless, if it would be helpful to know how to do this in the query for future reference if anyone knows how. Thanks!
  6. ChopinFan

    Concatenation Issue

    Thanks George, but I actually do have a space there in my actual sproc. It just didn't make it into my example above. Good catch, but without the concatenation, the whole thing runs fine.
  7. ChopinFan

    Concatenation Issue

    I need to concatenate into a string used as a select statement that creates a view, and I'm finding it doesn't like the syntax I am using. I already use the same syntax in a case when construct with no problem. Declare @SQL as varchar(2000) Set @SQL = 'Select FieldName From...' etc Declare...
  8. ChopinFan

    Memory Issue: Text or Varchar?

    Thanks for your valuable help!
  9. ChopinFan

    Memory Issue: Text or Varchar?

    Thanks for the good info. I am runnig SQL2K, but I don't have any need to manipulate or search through the text in any way, so it sounds like Text is the only viable option. It sounds like each text field takes up only 16 of the 8060 bytes available per row (only storing a pointer) while a...
  10. ChopinFan

    Memory Issue: Text or Varchar?

    If I'm understanding correctly, using text fields is the way to go. Am I to understand that if the total datalength yielded by the query you give is less than 8060, there's no problem?
  11. ChopinFan

    Memory Issue: Text or Varchar?

    Among other fields, there are seven in my table that could potentially contain 8,000 characters each and I am concerned about the memory size that any given row will take. I don't want to go over the memory limit. I understand that the Text datatype actually uses multiple data pages in the...
  12. ChopinFan

    Query to determine string length

    Excellent. "Datalength" does the trick. Thanks!
  13. ChopinFan

    Query to determine string length

    How do I query a text field to determine the maximum number of characters entered into it among all the records? Does SQL have an equivalent for a VBA Len() function? Thanks!
  14. ChopinFan

    criteria in query

    "I would like the report to print everyone with a total other than £0.00 in any of those four fields." It sounds like you're just looking for a where clause that says WHERE field1 <>0 OR field2 <>0 OR field3 <>0 etc. Am I understanding your need correctly?
  15. ChopinFan

    Pass through query with input parameters

    How do I get a pass through query to accept input parameters? I have no problem using the syntax below in regular SQL queries and it prompts the user for the information, but it isn't liking this in a pass through for some reason. --Input Parameters @Value1 varchar(500), @Value2 varchar(2) AS...

Part and Inventory Search

Back
Top