Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP SQL Syntax - Tuesday BrainFreeze
Message
 
 
To
11/07/2007 08:50:02
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01238981
Message ID:
01239208
Views:
8
>>>Wouldn't LEFT JOIN ON alltrim(upper(table1.aid))==alltrim(upper(table2.bid)) work regardless?
>>>
>>Yes, it would. Never used such construction in JOIN myself, but it would work regardless, you're right. Do you have NULL in any of ID fields?
>
>No you don't need alltrim() but may need upper(). You already used "==" operator, right? It ensures that trailing spaces are not important.
>Cetin

Cetin,

If Table1.aID is char 6 and Table2.bID is char 7 or vs. versa using == would result in 0 records match.

Personally I either use GUID or integer PKs, that's why I never had a need to use alltrim. But in Tracy's case (it's her problem) I'd say we either need to use alltrim or pad the shortest string to the longest string length.

You may check this http://www.berezniker.com/display/VFP/String+comparison+in+VFP for better than mine explanation.
If it's not broken, fix it until it is.


My Blog
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform