[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 799
  • Last Modified:

Access 2007 - Data Entry Property is not working within a subform.

I have a 2003 database that I am just started to open using Access 2007.  The main form consists of a subform for data entry of project notes.  When I open the main form the note subform opens correctly as a data entry format (where there is no records are shown).  When I click on the next record of the main form, the subform's data entry property stops working and shows the first project note record associated to the main form.  It was working perfect on 2003, I have not no changes since I opened it on 2007.  Any ideas?

(I hope I explained it clearly, ask me more questions if I did not.)
0
shrimpfork
Asked:
shrimpfork
  • 10
  • 7
2 Solutions
 
Rey Obrero (Capricorn1)Commented:
is the db located in a trusted location?

check the master/child link fields of the mainform/subform.
0
 
shrimpforkAuthor Commented:
capricorn1,
Yes the database is in a trusted location.  I just double checked the master/child link fields, and they are good.
0
 
Rey Obrero (Capricorn1)Commented:
can you upload your db?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
shrimpforkAuthor Commented:
I don't think so...it is a split database with 4 backend databases.  I also have security applied for users to login when they open the database.  I'm not sure if there is an easy way to do that.
0
 
shrimpforkAuthor Commented:
Let me see if I can reproduce it in another database.
0
 
Rey Obrero (Capricorn1)Commented:
you can create a db with the Form/subform and the corresponding tables with dummy data.

btw, how is the main form opened, in data entry mode ?
0
 
shrimpforkAuthor Commented:
I'm working on a dummy version of the database.  Stand by.

The main form is opened as
Data Entry = No.
0
 
shrimpforkAuthor Commented:
capricorn1,
OK, it took some doing and it is not pretty, but here is the cutout section of the database with the backend data attached into a single database. The main form is called "frmProjectNotes".  There might be a few VB mods hanging in there also (there are no VB mods required for this problem).
When you open the main form, the top portion should be blank for data entry.  If you go to the next record, the top subform now holds a record and is not in data entry mode.  Furthermore, if you add text to the entry box it will update they related record and then go into data entry format.
I hope you see the same on your end.

Subform-DataEntry.mdb
0
 
shrimpforkAuthor Commented:
Correction on the above VB comment above.  You will need to enable the VB to use the ADD Button.
0
 
shrimpforkAuthor Commented:
This version is cleaned up a little.
Subform-DataEntry.mdb
0
 
Rey Obrero (Capricorn1)Commented:
check your tables tblProjectInfo and tblProjectNotes

the relationship between the two is on ProjectID. see the Relationship diagram.
open the tables and you will see that there are no matching records based on ProjectID.

the matching fields are JobNumber on tblProjectInfo and ProjectID on tblProjectNotes



0
 
shrimpforkAuthor Commented:
I'm not sure if I follow you.  But if you look deeper into the table tblProjectNotes, I'm using the lookup modification and using the first column (hidden at column length 0") bound column 1 as the ProjectID.
 
0
 
Rey Obrero (Capricorn1)Commented:


oops, forget about my last post. there is  a lookup table on tblProjectNotes
0
 
Rey Obrero (Capricorn1)Commented:
see this, added textboxes for viewing record id.
added codes in the current event of the mainform.




Subform-DataEntry.mdb
0
 
Rey Obrero (Capricorn1)Commented:
shrimpfork,
i open the db in A2003 and it is behaving the same as in A2007.
0
 
shrimpforkAuthor Commented:
capricorn1,
I saw that adding the primary keys to the forms did nto really help.  It took code to "force" it to data entry. I was going to do the same by adding:

DoCmd.GoToRecord , , acNewRec

in the On Current event.

It is interesting that you saw the same behavior in A2003. We used this DB in our meeting last week with A2003 and it worked fine. After the meeting I updated the computers to A2007 and made no changes to that DB.
I would like to find out why this is happening. Any thoughts?
-Jed
0
 
shrimpforkAuthor Commented:
capricorn1,
I got it figured out. If the main form has a value set for the Order By property, then the Data Entry setting will not work on the subform.  (See Figure 1 attached).  I'm not sure why this behavior is acting this way, is this a possible bug A2007?  (We have been running it with a Order By setting for 1-2 years in A2003.)
I removed the entry in the Order By property on the main form and it started working fine.
-Jed

Data-Entry-Solution.jpg
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 10
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now