When creating table, we have to select the data type for each filed. Here is the list of data types in FoxPro 2.6.Data TypeDescriptionCharacter. To store string data type i.e., names, words.

Feb 28, 2002  RE: Data type mismatch!!!??? DEDMOD (Programmer) 27 Feb 02 22:51 I'd be happy to look at your form if you want to try to send to me at dedmod@msn.com, but it'd be helpful the have copies of the tables with sample data too, since otherwise it'd take a lot of effort to get it to the testing stage. Replace Command - Wiki for Microsoft Visual FoxPro development, software. REPLACE is one line. And a data type mismatch on a single line REPLACE with.

Can hold up to 254 characters. A-Z, a-z, 0-9, underscore & special symbols. Default length: 10Numeric. To store numerical value with decimal places. 0-9,. Can hold up to 20 digits.

Decimal part can be 0 to 18 digits. E.g. Usage: Marks, Roll NumberFloat.

It has signed numbers. Can hold up to 20 digits. E.g. Usage: percentage, averageDate.

Used to store date value. Default format dd/mm/yyLogical. Used to store Boolean value: True or False. Y, NMemo.

Used to store any amount of Text. The data stored in in a separate file with.fpt extension.General. Used to store text data, picture et.c,.

Used in FoxPro for Windows.

Hi all!In the command window the following works fineSELECT tblTargetTableyyy = 'divergcrtd' && the field divergcrtd is Lxxx =.F.REPLACE &yyy WITH xxx && works fineBut in code the following creates a Data type mismatch errorlcToField = RIGHT(ALLTRIM(crFldResult.FieldNames),;LEN(ALLTRIM(crFldResult.FieldNames)) - lnI - 4) && returns 'divergcrtd' tolcToFieldlcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) && Returns.F. TolcUsrDefValSELECT tblTargetTablefff = TYPE(lcUsrDefVal) && returns L to fff (just for check in debug)Replace &lcToField WITH lcUsrDefVal && generates Data type mismatch errorI cant see the difference between the command window code and theruntimecode.Whats wrong?RegardsChristinaFri, 01 Oct 2004 06:19:27 GMT. Hi all!

In the command window the following works fine SELECT tblTargetTable yyy = 'divergcrtd' && the field divergcrtd is L xxx =.F. REPLACE &yyy WITH xxx && works fine But in code the following creates a Data type mismatch error lcToField = RIGHT(ALLTRIM(crFldResult.FieldNames),; LEN(ALLTRIM(crFldResult.FieldNames)) - lnI - 4) && returns 'divergcrtd'to lcToField lcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) && Returns.F. To lcUsrDefVal SELECT tblTargetTable fff = TYPE(lcUsrDefVal) && returns L to fff (just for check in debug) Replace &lcToField WITH lcUsrDefVal && generates Data type mismatcherror I cant see the difference between the command window code and the runtimecode. Whats wrong?

Regards ChristinaFri, 01 Oct 2004 10:34:34 GMT. lcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) && Returns.F.

To lcUsrDefVal Right is a string function, not a logical one. When you say it 'returns'.f. Ok, there seems to be some confusion between the string values '.t.' (note the use of quotation marks and the logical values,.t. (noquotation marks), plus, to add to the confusion, the type functionevaluates only strings that contain variable names or string literals. Firstof all, let's observe that if we evaluate the string '.F.' With the typefunction, it will return the character L, because the string contains thename of the logical value.f., but if we evaluate the string '.f.'

, typewill return the character C, because the string (enclosed in ), containsanother string: quote-dot-f-dot-quote. Also note that when we make anassignment of a string value to a memory variable, the quotation marks arenot included in the memvar, they merely serve to inform the fox of what typeof data we're storing. Finally, type(.f.) will return an error.In your command line version, xxx contains a logical value, but in yourcode, lcUsrDefVal contains a string.

Replace &lcToField WITH &lcUsrDefValshould work.As an aside, I'd recommend reading up on name expressions in the on linehelp. Use them wherever possible instead of macro substitutions.

Your codewill execute faster, and be more readable and debugable.-Lew SchwartzVisual FoxPro SolutionsDatabase Programming and Designwww.clsystems.com718-336-8225. Thanks for your interest Lew! Yes Right is a string function and returns the string contained in lcFirstTry execpt the its first character. If lcFirstTry = 'R.F.' lcUsrDefVal brings to contain '.F.'

I have been investigating the problem further and a the thing I dont understand is why lcUsrDefVal randomly seems to contain '.F.' And randomly.F. Even if lcFirstTry allways contain '.F.'

Sugestions? Regards Christina lcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) && Returns.F. To lcUsrDefVal Right is a string function, not a logical one. When you say it'returns'.f. Hi Lew!You are right about the difference between the command line version vs incode.

But as said before I dontunderstand why lcUsrDefVal randomly seems to contain '.F.' (C) andrandomly.F. (L) even if lcFirstTry allways contain '.F.' (C) when idebug hovering the pointer over the variable lcUsrDefVal.OK I can live withtaht.But I need to learn if there is more than one way (writing something to thevariable) to determine the type (C or L or M.) of a variable.Imagine a variable lcX (type C) containing '.T.'

How can I write its contents to another variable lcY so the variable lcYcontains.T. (type L)Or if lcX = '2002-04-16 12:32:10' (type C) and I want lcY = 20:32:10 (type T) an so on with other types.RegardsChristina. Ok, there seems to be some confusion between the string values '.t.' (note the use of quotation marks and the logical values,.t. (no quotation marks), plus, to add to the confusion, the type function evaluates only strings that contain variable names or string literals.First of all, let's observe that if we evaluate the string '.F.'

With thetype function, it will return the character L, because the string contains the name of the logical value.f., but if we evaluate the string '.f.' ,type will return the character C, because the string (enclosed in ), contains another string: quote-dot-f-dot-quote. Also note that when we make an assignment of a string value to a memory variable, the quotation marks are not included in the memvar, they merely serve to inform the fox of whattype of data we're storing. Finally, type(.f.) will return an error.

In your command line version, xxx contains a logical value, but inyour code, lcUsrDefVal contains a string. Replace &lcToField WITH&lcUsrDefVal should work. As an aside, I'd recommend reading up on name expressions in the on line help. Use them wherever possible instead of macro substitutions. Your code will execute faster, and be more readable and debugable. Lew Schwartz Visual FoxPro Solutions Database Programming and Design www.clsystems.com 718-336-8225 Thanks for your interest Lew! Yes Right is a string function and returns the string contained in lcFirstTry execpt the its first character.

If lcFirstTry = 'R.F.' lcUsrDefVal brings to contain '.F.' I have been investigating the problem further and a the thing I dont understand is why lcUsrDefVal randomly seems to contain '.F.' Andrandomly.F. Even if lcFirstTry allways contain '.F.' Sugestions?

Regards Christina lcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) && Returns.F. To lcUsrDefVal Right is a string function, not a logical one. When you say it 'returns'.f.

Hi Lew! Holux gps gr 213 driver for mac download. You are right about the difference between the command line version vs in code. But as said before I dont understand why lcUsrDefVal randomly seems to contain '.F.' (C) and randomly.F.

(L) even if lcFirstTry allways contain '.F.' (C) when i debug hovering the pointer over the variable lcUsrDefVal.OK I can livewith taht. But I need to learn if there is more than one way (writing something tothe variable) to determine the type (C or L or M.) of a variable. Imagine a variable lcX (type C) containing '.T.' How can I write its contents to another variable lcY so the variable lcY contains.T. (type L) Or if lcX = '2002-04-16 12:32:10' (type C) and I want lcY = 2002-04-16 12:32:10 (type T) an so on with other types. Regards Christina Ok, there seems to be some confusion between the string values '.t.'

(note the use of quotation marks and the logical values,.t. (no quotation marks), plus, to add to the confusion, the type function evaluates only strings that contain variable names or string literals. First of all, let's observe that if we evaluate the string '.F.' With the type function, it will return the character L, because the string containsthe name of the logical value.f., but if we evaluate the string '.f.' , type will return the character C, because the string (enclosed in ),contains another string: quote-dot-f-dot-quote. Also note that when we make an assignment of a string value to a memory variable, the quotation marksare not included in the memvar, they merely serve to inform the fox of what type of data we're storing. Finally, type(.f.) will return an error.

In your command line version, xxx contains a logical value, but in your code, lcUsrDefVal contains a string. Replace &lcToField WITH &lcUsrDefVal should work. As an aside, I'd recommend reading up on name expressions in the onli ne help. Use them wherever possible instead of macro substitutions. Yourcode will execute faster, and be more readable and debugable. - Lew Schwartz Visual FoxPro Solutions Database Programming and Design www.clsystems.com 718-336-8225 Thanks for your interest Lew! Yes Right is a string function and returns the string contained in lcFirstTry execpt the its first character.

If lcFirstTry = 'R.F.' lcUsrDefVal brings to contain '.F.' I have been investigating the problem further and a the thing I dont understand is why lcUsrDefVal randomly seems to contain '.F.'

And randomly.F. Even if lcFirstTry allways contain '.F.' Sugestions? Regards Christina lcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) && Returns.F.to lcUsrDefVal Right is a string function, not a logical one. When you say it 'returns'.f. llY = (lcX = '.T.'

) When we do this sort of thing we don't bother with the dots. We use llY = (lcX = 'T') - David Dunetz SweetWARE Hi Lew! You are right about the difference between the command line version vsin code. But as said before I dont understand why lcUsrDefVal randomly seems to contain '.F.' (C) and randomly.F.

(L) even if lcFirstTry allways contain '.F.' (C) when i debug hovering the pointer over the variable lcUsrDefVal.OK I can live with taht. But I need to learn if there is more than one way (writing something to the variable) to determine the type (C or L or M.) of a variable. Imagine a variable lcX (type C) containing '.T.'

How can I write its contents to another variable lcY so the variable lcY contains.T. (type L) Or if lcX = '2002-04-16 12:32:10' (type C) and I want lcY = 2002-04-16 12:32:10 (type T) an so on with other types. Regards Christina Ok, there seems to be some confusion between the string values '.t.' (note the use of quotation marks and the logical values,.t. (no quotation marks), plus, to add to the confusion, the type function evaluates only strings that contain variable names or string literals. First of all, let's observe that if we evaluate the string '.F.' With the type function, it will return the character L, because the string contains the name of the logical value.f., but if we evaluate the string '.f.'

type will return the character C, because the string (enclosed in ), contains another string: quote-dot-f-dot-quote. Also note that when we make an assignment of a string value to a memory variable, the quotation marks are not included in the memvar, they merely serve to inform the fox ofwhat type of data we're storing.

Finally, type(.f.) will return an error. In your command line version, xxx contains a logical value, but in your code, lcUsrDefVal contains a string.

Replace &lcToField WITH &lcUsrDefVal should work. As an aside, I'd recommend reading up on name expressions in theon li ne help.

Use them wherever possible instead of macro substitutions. Your code will execute faster, and be more readable and debugable. - Lew Schwartz Visual FoxPro Solutions Database Programming and Design www.clsystems.com 718-336-8225 Thanks for your interest Lew! Yes Right is a string function and returns the string contained in lcFirstTry execpt the its first character.

If lcFirstTry = 'R.F.' lcUsrDefVal brings to contain '.F.' I have been investigating the problem further and a the thing Idont understand is why lcUsrDefVal randomly seems to contain '.F.' And randomly.F.

Even if lcFirstTry allways contain '.F.' Sugestions? Regards Christina lcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) && Returns.F. to lcUsrDefVal Right is a string function, not a logical one.

When you say it 'returns'.f. Hi David! Yes that works for converting C to L Is there a similar simple way for C to Y, C to I, C to N and so on. Regards Christina llY = (lcX = '.T.' ) When we do this sort of thing we don't bother with the dots. We use llY = (lcX = 'T') - David Dunetz SweetWARE Hi Lew!

You are right about the difference between the command line version vs in code. But as said before I dont understand why lcUsrDefVal randomly seems to contain '.F.' (C) and randomly.F.

(L) even if lcFirstTry allways contain '.F.' (C) wheni debug hovering the pointer over the variable lcUsrDefVal.OK I can live with taht. But I need to learn if there is more than one way (writing somethingto the variable) to determine the type (C or L or M.) of a variable. Imagine a variable lcX (type C) containing '.T.' How can I write its contents to another variable lcY so the variablelcY contains.T. (type L) Or if lcX = '2002-04-16 12:32:10' (type C) and I want lcY = 2002-04-16 12:32:10 (type T) an so on with other types. Regards Christina Ok, there seems to be some confusion between the string values'.t.'

(note the use of quotation marks and the logical values,.t. &.f.(no quotation marks), plus, to add to the confusion, the type function evaluates only strings that contain variable names or stringliterals. First of all, let's observe that if we evaluate the string '.F.' Withthe type function, it will return the character L, because the stringcontains the name of the logical value.f., but if we evaluate the string'.f.' type will return the character C, because the string (enclosed in )contains another string: quote-dot-f-dot-quote. Also note that when we makean assignment of a string value to a memory variable, the quotationmarks are not included in the memvar, they merely serve to inform the fox of what type of data we're storing. Finally, type(.f.) will return an error.

In your command line version, xxx contains a logical value, butin your code, lcUsrDefVal contains a string. Replace &lcToField WITH &lcUsrDefVal should work. As an aside, I'd recommend reading up on name expressions in the on li ne help. Use them wherever possible instead of macro substitutions.Your code will execute faster, and be more readable and debugable. - Lew Schwartz Visual FoxPro Solutions Database Programming and Design www.clsystems.com 718-336-8225 Thanks for your interest Lew! Yes Right is a string function and returns the string containedin lcFirstTry execpt the its first character. If lcFirstTry = 'R.F.'

lcUsrDefVal brings to contain '.F.' I have been investigating the problem further and a the thing I dont understand is why lcUsrDefVal randomly seems to contain '.F.' And randomly.F. Even if lcFirstTry allways contain '.F.'

Sugestions? Regards Christina lcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) && Returns.F. to lcUsrDefVal Right is a string function, not a logical one. When you say it 'returns'.f. lcX = '123.4567'.

C to N lnY = VAL(lcX). C to I lnY = INT(VAL(lcX)). C to Y lnY = ROUND(VAL(lcX), 4) Note that internally all numeric values are stored as N types (floating point).

The Integer and Currency data types only apply to fields. The INT and ROUND functions used above just give the appearance of the correctdata type. David Dunetz SweetWARE Hi David! Yes that works for converting C to L Is there a similar simple way for C to Y, C to I, C to N and so on. Regards Christina llY = (lcX = '.T.' ) When we do this sort of thing we don't bother with the dots.

We use llY = (lcX = 'T') - David Dunetz SweetWARE Hi Lew! You are right about the difference between the command line versionvs in code. But as said before I dont understand why lcUsrDefVal randomly seems to contain '.F.' (C) and randomly.F. (L) even if lcFirstTry allways contain '.F.' (C)when i debug hovering the pointer over the variable lcUsrDefVal.OK I canlive with taht. But I need to learn if there is more than one way (writing something to the variable) to determine the type (C or L or M.) of a variable.

Imagine a variable lcX (type C) containing '.T.' How can I write its contents to another variable lcY so the variable lcY contains.T. (type L) Or if lcX = '2002-04-16 12:32:10' (type C) and I want lcY =2002-04-16 12:32:10 (type T) an so on with other types. Regards Christina Ok, there seems to be some confusion between the string values '.t.' '.f.' (note the use of quotation marks and the logical values,.t.

&.f. (no quotation marks), plus, to add to the confusion, the typefunction evaluates only strings that contain variable names or string literals. First of all, let's observe that if we evaluate the string '.F.' With the type function, it will return the character L, because the string contains the name of the logical value.f., but if we evaluate the string '.f.'

type will return the character C, because the string (enclosed in )contains another string: quote-dot-f-dot-quote. Also note that when we make an assignment of a string value to a memory variable, the quotation marks are not included in the memvar, they merely serve to inform the fox of what type of data we're storing. Finally, type(.f.) will return an error. In your command line version, xxx contains a logical value,but in your code, lcUsrDefVal contains a string. Replace &lcToField WITH &lcUsrDefVal should work. As an aside, I'd recommend reading up on name expressions inthe on li ne help.

Use them wherever possible instead of macro substitutions. Your code will execute faster, and be more readable and debugable.

- Lew Schwartz Visual FoxPro Solutions Database Programming and Design www.clsystems.com 718-336-8225 Thanks for your interest Lew! Yes Right is a string function and returns the stringcontained in lcFirstTry execpt the its first character. If lcFirstTry ='R.F.' lcUsrDefVal brings to contain '.F.'

I have been investigating the problem further and a the thing I dont understand is why lcUsrDefVal randomly seems to contain '.F.' And randomly.F. Even if lcFirstTry allways contain '.F.' Sugestions? Regards Christina lcUsrDefVal = RIGHT(lcFirstTry,LEN(lcFirstTry) - 1) &&Returns.F. to lcUsrDefVal Right is a string function, not a logical one. When you sayit 'returns'.f.