Nested Sub Form error with goto next record EASY QUESTION [As RESOLVED as it can be]
Has anyone every found this happening to them.
Make a DB take a year over it ( :rolleyes: Yes I know!) give it out to 50 sets of users. With in 3 days bad reports are comeing back.
This is the bit that I need to understand: I have a form lets call it FrmMain1 this is bound to the table Branch and on the form is a hidden (Visible = False) text box bound to the Branch_ID Field. On to this form we added a subform this contains a hidden field too and you guess correctly it is the Foregn Key Branch_ID that links with the Parent form. Lets call this form FrmSubQuote1 this is the first form the user encounters that they are able to use anything on.
In this way we have locked records by User and Branch which is bliss for updates both ways.
on FrmSubQuote1 is a sub form, let us call it FrmSubGoods1 this form contains a list (Continouse forms!!) of the goods in the quote. The user can make limit changes here too.
So far so good in testing this was great. Then it started to come unstitched. We created 48 records (one each for the designated users) put the back end (data) and our front end (controls) on a CD with a mini install app and posted off about 45 copies. We uploaded the same files to the company FTP site and sat back to reseave praise.
It turns out that although the test user HO (Branch_ID = 1) work fine all other users found that forms refused to work correctly.
FrmSubQuote1 has an on_load event that currently looks like this
VB Code:
msgbox "On_load event!!!" , , "hi there"
DoCmd.GoToRecord , , acFirst
DoCmd.GoToRecord , , acLast
msgbox "End of On_load event!!!" , , "hi there"
due to the nature of the beast you can be sure that the last record is the one you were working on before FrmMain1 was opened. As a user you are now 2/3 of the way through a complex quoting processes and it will take you 5 to 10 mins to compleate each one rather than the previouse hour and a half.
Not a problem I hear you cry, but that's just it the msgbox pops up and says hallo twice and then it is time to inspect the records... but what's this?? If your branch_ID <> 1 then you are on record 1!!!! :eek:
The more I inspect the system the more I do not understand why it is not working.
I though perhaps the DB had bloated with old code so I imported forms and modules and reports and queries into a new DB and linked it to the BE... result - no change. :blush:
I don't know what the hell this DB is doing but there is the mood that jobs are resting on this now.
HELP!!!!!!!!!!!!!!!! :( :confused:
EDIT: It gets worse I sware it. Now on the faulty form the tiny sub form FrmMenu a sub form with just four Command Buttons on it fails to load and the refresh and reload button now reports "Access has caused an error and must close...".
what!? I don't get it this used to be a fully working DB. Now it is unusable.
helphelphelphelphelp.... :sick:
