|
Home > Archive > dBASE downloads > June 2005 > datatype mapping
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Roland Wingerter 2005-06-08, 9:25 am |
| I use Ken's exportdata.wfm on a regular basis and it is a great tool.
However AFAICS it is designed to handle dbase and paradox data types. It
would be even more useful if it could handle other datatypes as well. For
example, MS Access 2000 has some data types that are handled by the BDE, but
not by exportData.wfm. Under the subject "Data type mappings for CREATE
TABLE" the dBASE OLH lists 19 different data types that can be used in a
CREATE TABLE statement.
The zip file attached contains two tables:
- dbDatatype.dbf: datatypes used by dBase, MS Access 95 and MS Access 2000.
- dbDatatypeMapping.dbf: a mapping of these datatypes to one of the 19
dataTypes used by CREATE TABLE.
Maybe you feel like adding datatypes used by other databases, like mySQL,
Firebird and others and their local SQL equivalents.
Ken's code in exportdata.wfm is rather complex, and it is repeated in
several functions. How about writing a cc with a method for mapping
datatypes to local SQL syntax?
Roland
begin 666 dbDataTypes.zip
M4$L#!!0````(`(Z"<#+G>D;0`P(``/$7```.````9&)D871A='EP92Y$0D;E
ME\U*)#$4A0O&K3!K%Y)': 8&<7DK':L#E:1(I<7&5?6/(#@X=#LP/JCOH]V"
M(.;>B*=VWEUSTA_AYOZ<.KK]\9.JJGJJKJM<D-:-\5GI+;KM_?K?ZL$/?S99
M79^^_YV&Y=TF/?[-G_YX?CH\#,+Q#^>/U;JFWB@NULN;,U94?NY,M)J3$?1%
M&RCQ,H+6,XJDDXEY&4%/*?%_Q=!M:*RFEI,1M#,N\"J$KJVGN&!E!!U:*=5@
MKGW#JUB%A'DM7/S[Y9KF*5BOHW'&9QJ^B/[-BO!X$M#H>!+0Z'@2T.AX$M#H
M>!+0Z'@2T&C+".A"R[A>T6JUV>VRZJMTSK3-)<5]D>1%#"UQ%8;>%U^RCLL*
M@JZMT(L8V@5O^ *!T/TL1.'>"+JPP*!GE!<8>NMDKKB<H&BAV1%T88%!=;T0
MYS6"+BRP;M@.Z_O_7U(+=8V@#W5M?3)-=CTBZ%I/&>40"/K%A]3<.E<8FMIN
M1HRF,'3!+/*)H%!%TP"U"%R&8!05^$Z"@E,\W?'T$7? B";B)U,]Y?(VC!
M*.P#1?> )7)>7H>*3S0+4Z/*6@>KZ9<OTC*8^MV5^32:3G#J"4^70(SA5#EWX
M;D30O:.VM;D7/ 2"YM?B(1!T-/RP5AAZ!#O)H?=F02A !#W"!P>'3M8O^ (!
M;RTN,+#1)?H(S\CAL5Q+J^#D&5!+`P04````" `8?G R66I'M88!```Z"0``
M%0```&1B9&%T871Y<&5-87!P:6YG+D1"1IV5/4_#,!"&(\&*Q,R /# 4J0M?
M(\/%,8DE?[2.B^C8@8&E8NC0_B#^)TD;A4+OC2-NBYY[<W'NWO/YQ]GE399E
M7]ESQ@5)62K'HCZ*U6:
UV7V^(RZO?S_7<U/OUIO5ED\_R;\09&85"12RHD R
MJC!9WS*8%M%K)X.RRD5$&=T^<ED@U$2AI+9D)MOICJN<:T=AR8 #-3Z?K*?W
MG++%^O1CCZCW1I>!D58@=:\S^KQX EQ6TS`!+)5O6884EQ04-G'J9['+4%
M*2VI(]D9CPN_R U\^XOQ%-&(=)@E/1T0^V I1E4(JZS_2[L)>P"]*@/-*HU&
MOQ,_`;%V496@42DJC"^U) -H8K:-=R5B(RHW8I@S0HP]G?!S*X[J#;2Z$]\-
MB%\I@.(C*C=BX,Q$96ZN?B(E]D[!_9>@PBULCGO14!6T1-;H,$..*!)[;&;1
MG_D1G#DH.-@B6;FN?,#+H&[N&J. 92VP,3HCQ\DO3Q'Y,;,^
HW?*_AQ+8%&TD
MC(%-<43!57? U#5!+`0(4`!0````(`(Z
"<#+G>D;0`P(``/$7```.````````
M``$`( ````````!D8F1A=&%T>7!E+D1" 1E!+`0(4`!0````(`!A^
<#)9:D>U
MA@$``#H)```5```````
```$`( ```"\"``!D8F1A=&%T>7!E36%P<&EN9RY$
80D902P4&``````(``@!_````Z ,`````
`
end
| |
| Roland Wingerter 2005-06-08, 9:25 am |
| Roland Wingerter wrote:
> - dbDatatype.dbf: datatypes used by dBase, MS Access 95 and MS Access
> 2000.
-----
Correction: dBASE, Paradox, Access 97 and Access 2000.
| |
| Ken Mayer [dBVIPS] 2005-06-08, 9:25 am |
| Roland Wingerter wrote:
> I use Ken's exportdata.wfm on a regular basis and it is a great tool.
> However AFAICS it is designed to handle dbase and paradox data types. It
> would be even more useful if it could handle other datatypes as well. For
> example, MS Access 2000 has some data types that are handled by the BDE, but
> not by exportData.wfm. Under the subject "Data type mappings for CREATE
> TABLE" the dBASE OLH lists 19 different data types that can be used in a
> CREATE TABLE statement.
Well, I got sort of lazy, and didn't want to try to deal with the
gillions of permutations ... <g> (Not to mention I couldn't test most of
them, not having those various database types.)
> The zip file attached contains two tables:
>
> - dbDatatype.dbf: datatypes used by dBase, MS Access 95 and MS Access 2000.
> - dbDatatypeMapping.dbf: a mapping of these datatypes to one of the 19
> dataTypes used by CREATE TABLE.
>
> Maybe you feel like adding datatypes used by other databases, like mySQL,
> Firebird and others and their local SQL equivalents.
>
> Ken's code in exportdata.wfm is rather complex, and it is repeated in
> several functions. How about writing a cc with a method for mapping
> datatypes to local SQL syntax?
If someone wanted to fix that, it'd be great. I knew as I was writing
the code that it wasn't the most efficient means of handling it ... <g>
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase
| |
| Roland Wingerter 2005-06-08, 9:25 am |
| Ken Mayer [dBVIPS] wrote:
> Roland Wingerter wrote:
>
> If someone wanted to fix that, it'd be great. I knew as I was writing
> the code that it wasn't the most efficient means of handling it ...
> <g>
-------
I am in the process of separating the export methods from the form and
putting them into a separate exportData.cc, as suggested by Michael Nuwer
some time ago. This way the methods could be used independently of the form,
or someone could use the existing methods and create their own form (e.g.
with a user interface in a different language). I will post the cc when it's
ready.
Roland
| |
| Ken Mayer [dBVIPS] 2005-06-08, 9:25 am |
| Roland Wingerter wrote:
> Ken Mayer [dBVIPS] wrote:
>
>
> -------
> I am in the process of separating the export methods from the form and
> putting them into a separate exportData.cc, as suggested by Michael Nuwer
> some time ago. This way the methods could be used independently of the form,
> or someone could use the existing methods and create their own form (e.g.
> with a user interface in a different language). I will post the cc when it's
> ready.
Shoot, if you're going that far, perhaps looking into modifying the form
to use those? <g>
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase
| |
| Roland Wingerter 2005-06-08, 9:25 am |
| Ken Mayer [dBVIPS] wrote:
>
> Shoot, if you're going that far, perhaps looking into modifying the
> form to use those? <g>
------
I won't touch the user interface of the form, it will remain unchanged. I
only changed the code in the OutputButton_onClick
, because the methods
called are now in an external cc.
If you have some new ideas, I suggest to wait for the new version. I am
hoping to post it later today.
Roland
| |
| Ken Mayer [dBVIPS] 2005-06-08, 9:25 am |
| Roland Wingerter wrote:
> Ken Mayer [dBVIPS] wrote:
>
>
> ------
> I won't touch the user interface of the form, it will remain unchanged. I
> only changed the code in the OutputButton_onClick
, because the methods
> called are now in an external cc.
Quite alright. The interface would be tricky to modify because of the
weird way it was coded.
> If you have some new ideas, I suggest to wait for the new version. I am
> hoping to post it later today.
Sorry. I haven't really looked at it all that closely in awhile. I've
had my brain stuffed in other code ... <g>
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase
| |
| Roland Wingerter 2005-06-08, 9:25 am |
| Roland Wingerter wrote:
> I suggest to wait for the new version. I
> am hoping to post it later today.
------
Just posted it in dbase.shared-code.
Roland
| |
| Roland Wingerter 2005-06-08, 9:25 am |
| Ken Mayer [dBVIPS] wrote:
>
> Quite alright. The interface would be tricky to modify because of the
> weird way it was coded.
------
Well, if yout say so... ;-) But I am not sure I know what you mean.
> Sorry. I haven't really looked at it all that closely in awhile.
------
No problem.
> I've had my brain stuffed in other code ... <g>
------
Sure, I am not surprised. <g>
Roland
| |
| Ken Mayer [dBVIPS] 2005-06-08, 9:25 am |
| Roland Wingerter wrote:
> Ken Mayer [dBVIPS] wrote:
>
>
> ------
> Well, if yout say so... ;-) But I am not sure I know what you mean.
Some of the code to manipulate the UI is buried in the onClick events
and such. It's complex and odd because of the way it sort of grew (kind
of the way the rest of the code came together). It wasn't well planned
or designed.
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase
| |
| Roland Wingerter 2005-06-08, 9:25 am |
| Ken Mayer [dBVIPS] wrote:
> Roland Wingerter wrote:
>
> Some of the code to manipulate the UI is buried in the onClick events
> and such. It's complex and odd because of the way it sort of grew
> (kind of the way the rest of the code came together). It wasn't well
> planned or designed.
-----
Ken,
thanks for the enlightenment. ;-)
Roland
| |
| Ken Mayer [dBVIPS] 2005-06-08, 9:25 am |
| Roland Wingerter wrote:
> Ken Mayer [dBVIPS] wrote:
>
>
> -----
> Ken,
>
> thanks for the enlightenment. ;-)
This was one of those projects where I started with a basic idea in
mind, and then as I posted things to the newsgroups, the folk who were
working with/testing it made suggestions and such, and so I kept adding
to it, but I didn't plan it as well as I could have.
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase
|
|
|
|
|