Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How to handle .NULL. values in ODBC
Message
 
 
À
23/05/2001 10:45:29
Patrick O'Neil
American Specialty Information Services
Roanoke, Indiana, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00510117
Message ID:
00510433
Vues:
11
Patrick,

I'm not sure why ODBC is giving you a character column. Are you positive the VFP cursor columntype is not numeric? We use Sybase and SQL Server backends and a view setup against those sources give a datatype that matches the server dataype and sets the column as nullable in the local cursor.

You could use an expression as the field value to convert the nulls, but if it's an updateable view you'll have to handle the updates with your own cooked up SPT instead of using TableUpdate().

>In the Access table one of the columns (fields) that i want to use
>is a numeric field (double or long, for example). in this column,
>it may or may not have .null. values in the access table.
>
>if none of the (access) rows have .null. values in this (numeric)
>column, the corresponding column in my vfp remote view will be
>created as a numeric field. if there are (some) .null. values, my vfp
>remote view will be created as a character field.
>
>is it possible to force the corresponding column in the vfp view
>to be numeric and default to a certain value in the view, if the
>access value is .null. ?
df (was a 10 time MVP)

df FoxPro website
FoxPro Wiki site online, editable knowledgebase
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform