Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Copy to array problem
Message
From
09/07/2004 12:39:27
 
 
To
09/07/2004 11:10:38
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00922521
Message ID:
00922570
Views:
25
COPY TO ARRAY has problems with Memo fields. I don't have a copy of FPD 2.5 at hand but in FPW2.6 what I "THINK" happens is that all memo fields are moved to the last columns in the array and are populated with .F. (this is what happened with my first experiment on this).

If you send me the table I may be able to find a pattern for you when I get back home to an FPD archive.

HTH............Rich


>Is there a known problem with Copy to array in Fox/DOS 2.5? When sing copy to array, logical .F. appears in the array when no logical fields are being copied. In addition, the appearance of these values pushes the remaining data farther down, leading to invalid type errors when later accessing the data.
>
>I haven't been able to find any cause for this, or a solution. The program has 10-20 users, running on a Win 2000 SP 4 machine via Windows Terminal Server. Can anyone tell me why I'm getting this and how to get around it?
>
>This is a listing of one such array, look at 5,1-5,4 and 6,5.
>
>CLSR        Priv   A                                         CROSTER
>  (   1,   1)     C  "     14430"
>  (   1,   2)     C  "0220031113"
>  (   1,   3)     C  " 1 4POFM1210  "
>  (   1,   4)     C  " "
>  (   1,   5)     D  11/10/2003
>  (   1,   6)     C  "*"
>  (   1,   7)     C  "*"
>  (   1,   8)     C  "*"
>  (   1,   9)     C  "P"
>  (   1,  10)     C  "P"
>  (   1,  11)     C  " "
>  (   2,   1)     C  "     14430"
>  (   2,   2)     C  "0220031113"
>  (   2,   3)     C  " 1 4POFM1210  "
>  (   2,   4)     C  " "
>  (   2,   5)     D  11/17/2003
>  (   2,   6)     C  "P"
>  (   2,   7)     C  "P"
>  (   2,   8)     C  "P"
>  (   2,   9)     C  "P"
>  (   2,  10)     C  "P"
>  (   2,  11)     C  " "
>  (   3,   1)     C  "     14430"
>  (   3,   2)     C  "0220031113"
>  (   3,   3)     C  " 1 4POFM1210  "
>  (   3,   4)     C  " "
>  (   3,   5)     D  11/24/2003
>  (   3,   6)     C  "A"
>  (   3,   7)     C  "P"
>  (   3,   8)     C  "P"
>  (   3,   9)     C  "H"
>  (   3,  10)     C  "H"
>  (   3,  11)     C  " "
>  (   4,   1)     C  "     14430"
>  (   4,   2)     C  "0220031113"
>  (   4,   3)     C  " 1 4POFM1210  "
>  (   4,   4)     C  " "
>  (   4,   5)     D  12/01/2003
>  (   4,   6)     C  "A"
>  (   4,   7)     C  "P"
>  (   4,   8)     C  "P"
>  (   4,   9)     C  "P"
>  (   4,  10)     C  "P"
>  (   4,  11)     C  " "
>  (   5,   1)     L  .F.
>  (   5,   2)     L  .F.
>  (   5,   3)     L  .F.
>  (   5,   4)     L  .F.
>  (   5,   5)     C  "     14430"
>  (   5,   6)     C  "0220031113"
>  (   5,   7)     C  " 1 4POFM1210  "
>  (   5,   8)     C  " "
>  (   5,   9)     D  12/08/2003
>  (   5,  10)     C  "P"
>  (   5,  11)     C  "P"
>  (   6,   1)     C  "P"
>  (   6,   2)     C  "P"
>  (   6,   3)     C  "A"
>  (   6,   4)     C  " "
>  (   6,   5)     L  .F.
>  (   6,   6)     C  "     14430"
>  (   6,   7)     C  "0220031113"
>  (   6,   8)     C  " 1 4POFM1210  "
>  (   6,   9)     C  " "
>  (   6,  10)     D  12/15/2003
>  (   6,  11)     C  "P"
>  (   7,   1)     C  "P"
>  (   7,   2)     C  "A"
>  (   7,   3)     C  "P"
>  (   7,   4)     C  "P"
>  (   7,   5)     C  " "
>  (   7,   6)     L  .F.
>  (   7,   7)     C  "     14430"
>  (   7,   8)     C  "0220031113"
>  (   7,   9)     C  " 1 4POFM1210  "
>  (   7,  10)     C  " "
>  (   7,  11)     D  01/05/2004
>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform