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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Is Paradox 5.0 case sensitive?
- Thread starter troyu
- Start date
- Thread starter
- #3
I think you may be wrong here: I have found that it is:
I was making some changes to some code within a form that contained a tableframe. When adding some new fields to this tableframe, the tableframe header got renamed automatically to the default name... Thinking that I should rename this back to what it was originally, I did so, but I named it with a capital.
<<*TSK TSK* Bad move troyu.>>
Even though the code appeared to be calling this tableframe by name, it was actually calling it with a lower case and not uppercase header.... I renamed this tableframe with lowercase, and it is now working fine....
I was making some changes to some code within a form that contained a tableframe. When adding some new fields to this tableframe, the tableframe header got renamed automatically to the default name... Thinking that I should rename this back to what it was originally, I did so, but I named it with a capital.
<<*TSK TSK* Bad move troyu.>>
Even though the code appeared to be calling this tableframe by name, it was actually calling it with a lower case and not uppercase header.... I renamed this tableframe with lowercase, and it is now working fine....
troyu,
Some operations are case-sensitive; others aren't. Searching for values is almost always case sensitive, but object names should not be.
I suggest using table aliases in your data model to prevent your data containers from being renamed. to do this, right click the icon in the data model designer, choose the first item in the menu and then enter a name for the object in question.
This will make your forms and reports more portable.
Hope this helps...
-- Lance
Some operations are case-sensitive; others aren't. Searching for values is almost always case sensitive, but object names should not be.
I suggest using table aliases in your data model to prevent your data containers from being renamed. to do this, right click the icon in the data model designer, choose the first item in the menu and then enter a name for the object in question.
This will make your forms and reports more portable.
Hope this helps...
-- Lance
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question