I found out, the problem is not in the numeric part of the names, rather, names containing uppercase letters cause the problem. Again, is it convention that database field names should be lowercase?
On Mar 7, 9:46 am, StUStD <hjansen...@gmail.com> wrote: > I experience inserting and updating problems (only explicit SQL > statements in de dbadmin work, forms don't) with fieldnames like B1x, > B1y, B2x, B2y, etc, only to find out that fieldnames with numbers > don't work... Is this default behaviour, convention, or caused by a > bug? Thanks.
