General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
>>>I've got a class method that builds a SQL statement on the fly based on metadata. The field list has to be built dynamically before issuing the SQL call, as in:
>>>
>>>SELECT &lcFieldList ;
>>> FROM &lcTable ;
>>> INTO CURSOR lvNormalized
>>>
>>>The field list has to be dynamically built from a table of field mappings to normalize the data before moving it to a data warehouse. It all works fine, the hard part is done. But early on in testing I found that the lcFieldList variable can end up exceeding 254 characters, which generates an error. I've gotten around it in a cheesy kind of way, but I was wondering if anyone had any ideas on a more permanent solution.
>>>
>>>TIA
>>
>>Is it exceding 254 Characters or 254 Fields? Cause a string variable can contain like 16 million characters.
>>
>>BOb
>
>Yes, but there is a limit to the length of a command that can be executed with Macro substitution. Don't remember exactly, but 254 sounds like a good candidate.
Ah... then he should probably build the whole SELECT statement into a string variable then execute it with the eval() function.
BOb
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only