|
|
 | | From: | Robert Kersting | | Subject: | dQuery error | | Date: | Sun, 02 Jan 2005 02:01:11 GMT |
|
|
 |
Hey all.
I'm getting an error while using the dQuery export function. There
are 3 tables that I am having trouble with. The error is as follows:
Invalid subscript reference.
File: dWizExport.wfo
Routine: QWIZEXPORTFORM::CANCOPYFIELDVALUE
Line: 2577
Several others follow if I hit ignore, but I suspect that this is the
killer.
The tabes are being copied from dbf files (from an old legacy app from
15 years ago) to postgresql. It is quite possible that some of the
field names are the culprits, but I haven't played with it yet and
won't have time. Here are a couple of the structures to play with for
anyone who wishes to tinker.
Structure for table N:\dbase\winrslt.dbf
Table type DBASE
Version 4
Number of rows 836
Last update 12/08/1998
----------------------------------------------------------
Field Field Name Type Length Dec Index
1 SECTIONNUM CHARACTER 15 Y
2 UPSECTION CHARACTER 15 Y
3 PHASE_CODE NUMERIC 1 N
4 CONNECTION CHARACTER 1 N
5 EQUIP_REF CHARACTER 20 N
6 MILES2SRC NUMERIC 6 2 N
7 LENGTH NUMERIC 6 2 N
8 PRI_KV_A NUMERIC 8 2 N
9 PRI_KV_B NUMERIC 8 2 N
10 PRI_KV_C NUMERIC 8 2 N
11 PRI_KV NUMERIC 8 2 N
12 BASEVOLT_A NUMERIC 8 2 N
13 BASEVOLT_B NUMERIC 8 2 N
14 BASEVOLT_C NUMERIC 8 2 N
15 BASEVOLT NUMERIC 8 2 N
16 SECTDROP_A NUMERIC 8 2 N
17 SECTDROP_B NUMERIC 8 2 N
18 SECTDROP_C NUMERIC 8 2 N
19 SECTDROP NUMERIC 8 2 N
20 CRNTDROP_A NUMERIC 8 2 N
21 CRNTDROP_B NUMERIC 8 2 N
22 CRNTDROP_C NUMERIC 8 2 N
23 CRNTDROP NUMERIC 8 2 N
24 THRUAMPS_A NUMERIC 8 2 N
25 THRUAMPS_B NUMERIC 8 2 N
26 THRUAMPS_C NUMERIC 8 2 N
27 THRUAMPS NUMERIC 8 2 N
28 CAPACITY_A NUMERIC 8 2 N
29 CAPACITY_B NUMERIC 8 2 N
30 CAPACITY_C NUMERIC 8 2 N
31 CAPACITY NUMERIC 8 2 N
32 THRU_KW_A NUMERIC 8 2 N
33 THRU_KW_B NUMERIC 8 2 N
34 THRU_KW_C NUMERIC 8 2 N
35 THRU_KW NUMERIC 8 2 N
36 KVAR_A NUMERIC 8 2 N
37 KVAR_B NUMERIC 8 2 N
38 KVAR_C NUMERIC 8 2 N
39 KVAR NUMERIC 8 2 N
40 P_FACTOR_A NUMERIC 8 2 N
41 P_FACTOR_B NUMERIC 8 2 N
42 P_FACTOR_C NUMERIC 8 2 N
43 P_FACTOR NUMERIC 8 2 N
44 LOSS NUMERIC 8 2 N
45 KW_A NUMERIC 8 2 N
46 KW_B NUMERIC 8 2 N
47 KW_C NUMERIC 8 2 N
48 KW NUMERIC 8 2 N
49 SECTKVAR_A NUMERIC 8 2 N
50 SECTKVAR_B NUMERIC 8 2 N
51 SECTKVAR_C NUMERIC 8 2 N
52 SECTKVAR NUMERIC 8 2 N
53 CONS_ON_A NUMERIC 8 N
54 CONS_ON_B NUMERIC 8 N
55 CONS_ON_C NUMERIC 8 N
56 CONS_ON NUMERIC 8 N
57 CONS_OFF_A NUMERIC 8 N
58 CONS_OFF_B NUMERIC 8 N
59 CONS_OFF_C NUMERIC 8 N
60 CONS_OFF NUMERIC 8 N
61 CALCBASEKW NUMERIC 8 2 N
62 FAULT_IMP NUMERIC 12 4 N
63 MINPHS_GRD NUMERIC 12 4 N
64 MAXFLT_LG NUMERIC 12 4 N
65 MAXFLT_LL NUMERIC 12 4 N
66 MAXFLT_LLG NUMERIC 12 4 N
67 MAXFLT_3LG NUMERIC 12 4 N
68 POSSEQ_RES NUMERIC 12 4 N
69 POSSEQ_REA NUMERIC 12 4 N
70 ZEROSEQRES NUMERIC 12 4 N
71 ZEROSEQREA NUMERIC 12 4 N
----------------------------------------------------------
** Total ** 617
And a little shorter one:
Structure for table N:\dbase\recl.dbf
Table type DBASE
Version 4
Number of rows 1060
Last update 12/13/2004
----------------------------------------------------------
Field Field Name Type Length Dec Index
1 CNUM NUMERIC 4 Y
2 SIZE NUMERIC 4 N
3 MAKE CHARACTER 4 N
4 SERIAL CHARACTER 15 Y
5 TYPE CHARACTER 4 N
6 PURCHASED DATE 8 N
7 STATUSDATE DATE 8 Y
8 COUNTDATE DATE 8 N
9 POLE_NUM CHARACTER 8 Y
10 OLDPOLE CHARACTER 6 N
11 STATUS CHARACTER 7 N
12 COUNTSET NUMERIC 4 N
13 COUNTNOW NUMERIC 4 N
----------------------------------------------------------
** Total ** 85
BTW. They look better in a non-proportional font and I trimmed 15
characters between fieldname and type (for those who might create
tables from the disp stru output).
I'm going to convert these the old-fashioned way for now and
eventually run them through an automated conversion process, but I
thought I'd let you know about the issue.
Rob
|
|
| | From: | Geoff Wass | | Subject: | Re: dQuery error | | Date: | Sun, 2 Jan 2005 21:40:16 -0500 |
|
|
| Robert Kersting wrote:
> Hey all.
>
> I'm getting an error while using the dQuery export function. There
> are 3 tables that I am having trouble with. The error is as follows:
>
> I'm going to convert these the old-fashioned way for now and
> eventually run them through an automated conversion process, but I
> thought I'd let you know about the issue.
>
> Rob
Robert,
Just to help dBI, can you tell us which version of dQuery this is? Thanks!
--
:-)
----------
Geoff Wass (dBVIPS)
Montréal, Québec, Canada
==========
=======
====
=
More dBASE information at http://geocities.com/geoff_wass
Please reply in the news groups only.
Have you backed up your work?!
=
====
=======
==========
|
|
| | From: | Robert Kersting | | Subject: | Re: dQuery error | | Date: | Mon, 03 Jan 2005 13:46:57 GMT |
|
|
| Hmmmmm.... The latest. It came with Plus 2.5 and the patch.
Looking for a version number
core version: b1804
dquery version 1241
Dated 11/21/2004
Rob
On Sun, 2 Jan 2005 21:40:16 -0500, "Geoff Wass"
wrote:
>
>Just to help dBI, can you tell us which version of dQuery this is? Thanks!
|
|
|
