I have a have a database where one .mdb file is used strictly to record information on people, kind of like a roster - one entry person. Another .mdb is used for transactions, is linked to the roster.mdb, and uses dlookup() to find information about the person to fill part of the transaction file based on the person's record id number. Pretty straight forward.
There are about 75,000 records in the roster.mdb, and that will only go up. However, if the person's record number is greater than 65536, the dlookup returns nulls in all fields.
I know the records are there, and records above the 65536 limit will print on reports, so the system is able to access them.
The record number field is an autonumber, and every field or variable involved in either .mdb is set to long integer.
I have a combo box on the transaction screen that links to the roster.mdb. Clicking the pull-down displays the person's ID number, last name, first name, middle name, and date of birth. It displays all records through 65536, and *part* of 65537.
Some of the information in the roster must be incorporated in the transaction file (for example, we track address history), so it's no good just using the ID number. Some repeatable information must be entered with each transaction record, and I'd like to reduce operator "creativity" by having it drawn from the roster file.
This is the first time I have dealt with a lookup on a file this size. Have I overlooked an inherent integer-only limit to the number of records that can be used in a dlookup? or combo box? I don't remember reading it, but that doesn't mean much. The roster.mdb file is only about 25megs, nowhere near the 1gb limit, and contains only the roster table with links to a reference table with valid city names and such things, so it's not the file size or number of objects in the file. Everything else about the forms, code and reports works, but for the records after 65536, I'm in a world of hurt.
Thanks for any help.
-Terry
There are about 75,000 records in the roster.mdb, and that will only go up. However, if the person's record number is greater than 65536, the dlookup returns nulls in all fields.
I know the records are there, and records above the 65536 limit will print on reports, so the system is able to access them.
The record number field is an autonumber, and every field or variable involved in either .mdb is set to long integer.
I have a combo box on the transaction screen that links to the roster.mdb. Clicking the pull-down displays the person's ID number, last name, first name, middle name, and date of birth. It displays all records through 65536, and *part* of 65537.
Some of the information in the roster must be incorporated in the transaction file (for example, we track address history), so it's no good just using the ID number. Some repeatable information must be entered with each transaction record, and I'd like to reduce operator "creativity" by having it drawn from the roster file.
This is the first time I have dealt with a lookup on a file this size. Have I overlooked an inherent integer-only limit to the number of records that can be used in a dlookup? or combo box? I don't remember reading it, but that doesn't mean much. The roster.mdb file is only about 25megs, nowhere near the 1gb limit, and contains only the roster table with links to a reference table with valid city names and such things, so it's not the file size or number of objects in the file. Everything else about the forms, code and reports works, but for the records after 65536, I'm in a world of hurt.
Thanks for any help.
-Terry