>Christof,
>THis is precisely what we were looking for. The reason we didn't
>want to use afields() was that we are putting this code in the
>validation of the database for every single field. To create up to
>255 arrays per table seems a bit overburdening. This will solve the
>issue cleanly and precisely. When we create the app, we do not
>know the size of the field nor how many decimal points there will
>be beforehand.


But you're NOT creating up to 255 arrays per table, you're creating an array PER TABLE. You might want to re-check the help file for AFIELDS() as I think you are mistaken on its use/function.