Sorry for the double posting, but I just realized this might not belong in the "Database Development" Forum, since I'm not Developing a database, but just trying to successfully read one via VB.Net or VB6.

So:


Does anybody have an example of retrieving Records from a Database {Filemaker, via ODBC} that was designed with fields that contain "Repeating Fields"?

I've spent the last three days playing with code that would attempt to return the results of an SQL statement, but it would err out after n records were returned. Yesterday, I copied the file, and started redifining the fields.

I first thought it might be because the field names were made with spaces, but after renaming, It still would fault.

I then looked at the database in its app in table format, noticed some fields that had a name spanning multiple cells.

So, Checking those specific field formats, I stumbled across the setting for "Repeating Fields" were selected. Removing that selection, and running my code, I returned the 254 records that Were supposed to be returned.'

So, I know know that its these "Repeating Fields" Fields are the culpret of the bombings, and I theorize that when it returns a record with more than 1 sub field containing data in the "Repeating field" field, it faults because it has no place to place the extra data, assuming up to this point it was useing a row with only N fields defined.

Now, Unfortunately, I also saw that when the repeating fields selection was deselected, the data adjacent to the data in the first column of this mutant field, instead of {hopefully} merging into one cell, actually "poofed" into thin air, causeing some fumes to appear suspiciously close to my ears, but smelling something like burning hair.

So, I know that I can't go to the designer of the Companies Database and tell him to fix his "repeating Columns", therefore I really need to figure a way of dealing with it.

So, again, anybody here with any hint of what I can do?