DisplayEntryOptions(repost)

Programming is not part of my job description. I occasionally write programs to meet simple local departmental needs. This means I am a novice programmer. It also means that sometimes I forget how to do things I have already figured out how to do in the past. I am looking for a solution that will permit me plug in the real world data and duplicate the functions in these forms onto similar forms that use a different filter and background color. Details of the program and problem are contained in the attachment “Collateral dBase [login to view URL]?. The file “Collateral Working [login to view URL]? shows how the change between screens should look. The file “Collateral Adjusted [login to view URL]? is the file I want updated/corrected. The master table is HeaderData. The child table is TransactionData. There is a one-to-many relationship with multiple TransactionData records permitted for a single HeaderData record. The “Loan Information?? screen (HeaderData) is used to enter, modify, and view loan information and control access to the transaction screens (TransactionData). When the user goes to a transaction enter/modify/view screen, select loan information is displayed and a subform is used to enter the transaction data. Problem 1: Records directly entered into the database display properly when going from the loan information screen to the transaction screen. Records imported into the tables (the real world data I cannot permit programmers to view) do not display header information when the user goes to the transaction screens. Problem 2: The user wants to ensure key fields are entered properly by requiring the data to be entered twice before it is accepted into the field. Problem 3: Can the auto-complete feature found in many Microsoft programs (Excel, Word) be used to complete information in selected fields? ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). 4) Code should be fully documented and available to buyer. Buyer should be advised of any potential problems that would make transporting the code to other modules in the database. ## Platform Microsoft Access 2003 running on Windows XP professional on domain network.