dim

[Jose Lerebours]

> Test Joe's suggestion.
> 
> 1. Dim foobar(20):myfile(a1 ) passes syntax check
> 
> 2. Fails to get any data from myfile.  
> 
> Need to use 2 arrays to get data and then backfill the first if there is
> data in the second.
> 

This is a prime example of where proper planning and normalizing your
database is a good practice.  There are instances where associated 
fields are your friends and they sure help write a quick header/detail %like%
application (if you do not mind wasting disk space) but you run the risk
of blocking yourself in - as it is the case here.

While more work is involved, I have always preferred to use a separate 
table (filePro file) where I can keep detail information.  Using a separate
table gives you endless capacity (or as much as your disk can hold).  

Is this too involved for you to simply port the data over to a separate table?

That said, there are times where use of associated fields cannot be beat!

Oh, it went from 10 to 20 ... How long before it goes to 40,50,60 ... ???

Regards,


--
Jose Lerebours
http://www.fpgroups.com
954-559-7186
filePro + PHP Solution Developer