Dimension or declare array

[SnyAc]

I have found a situation where an array is being created using AFIELDS() and then re-dimensioned larger to add fields to the array in order to create a temporary table with the additional fields. VFP9 seems to want to clear the array when it is re-dimensioned (all elements set to logical false) so the subsequent CREATE TABLE FROM ARRAY fails with a syntax error.

Any ideas on why the array would get re-initialized on the re-dimension?



Andy Snyder
SnyAc Software Services

http://www.snysoft.com

 

[Mike Lewis]

Andy,

I've never seen the behaviour you are describing. Can you post the minimum code needed to reproduce the problem?

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[RickBorup]

The newly added array elements will have initial values of logical False, but the original array element values should not be disturbed when the array is redimensioned. The following code does what I think you're describing and leaves the first set of array elements as is:

CREATE TABLE myTable ( cField1 c(10))
AFIELDS( laFields, "myTable")
DISPLAY MEMORY LIKE laFields && Array is [1,18] with values as expected
DIMENSION laFields(2,18)
DISPLAY MEMORY LIKE laFields && Original array values are still intact

Is it possible in your situation that a different array is being created or the original array is going out of scope?

-Rick

 

[StewartUK]

FYI - you need to copy the link to Mike's article (including the equals sign at the end) and paste it into your browser as the automatic linking hasn't included the equals sign.

Stewart

 

[GriffMG]

What you need to do is create another array, the size you need and then copy your data into it... at least that is what I would do.

Regards

Griff
Keep [Smile]ing

 

[AndyKr]

>>Any ideas on why the array would get re-initialized on the re-dimension?

Yes. Check the setting of SET COMPATIBLE.

IF it is ON (dBase) then arrays are re-initialized when re-dimensioned, if it is OFF (VFP) then they are not.

This is documented behavior - see the DECLARE command for details.

As an aside, SET COMPATIBLE ON is a setting that should NEVER be used in VFP - it affects the behavior of all sorts of things - see the Help file for the full list.

It was included in the language when dBase was a major competitor for FoxPro to enable dBase code to run directly. It has no other function or use but it does mess up VFP behaviors.


----
Andy Kramek
Visual FoxPro MVP

 

[SnyAc]

Andy... I think you hit the nail on the head. This is a complex app that includes a good bit of old legacy code. I am in the process of updating this application to get it ready for release in VFP9 format. I changed the use of afields() to an SQL select with no records to create the read-write cursor.

Thanks again for everyone's input.... always helpful.

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

 

[AndyKr]

Is anyone else having problems posting here? I cannot post anything

----
Andy Kramek
Visual FoxPro MVP

 

[Mike Gagnon]

Andy,

Is anyone else having problems posting here? I cannot post anything

What do you mean post? I can see your message above.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
ReFox XI (www.mcrgsoftware.com)