Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Connect to MS Access
Message
De
18/07/2005 12:22:45
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Versions des environnements
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Divers
Thread ID:
01033086
Message ID:
01033571
Vues:
18
>Hi Cetin,
>
>I have utilized the code that you pointed me to and was successful in creating the VFP tables from the Access database.
>
>I do, however, have a couple of questions regarding the results...
>
>Why would some of the fields come over as MEMO?
>
>and
>
>Is there a way to not have .NULL. values?
>
>TIA
>Vince

With ODBC UseMemoSize controls the maximum length of char fields (default 255, 1-255). ie:
lnHandle=SQLStringConnect(...)
CURSORSETPROP('UseMemoSize',255,0)
SQLExec(m.lnHandle,...,...)
Set null off
would help if explicitly .null. values are not in data.

You might try to workaround getting via ADO instead. ie:
LOCAL oRs as adodb.recordset
oCon = createobject("AdoDb.Connection")
oCon.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=..."
oCon.Open
oRS = oCon.Execute(...)

xDOM = NEWOBJECT('MSXML.DOMDocument')
oRS.Save(xdom, 1)
oRS.Close
oCon.close
XMLTOCURSOR(xdom.xml, "MyCursorName", 1028)
SELECT MyCursorName
BROWSE
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform