How to test and debug a split database

[ChrisTheIntern]

Quick question from a newbie: I have a split database with forms and subforms that I am constantly adding new features to. I work exclusively on my local copy and make sure things run fine before I link the tables and send out the updated front end. But sometimes, even if the features worked fine on my local copy, I discover problems when multiple people start using it.

My current testing method is to wait until my coworker leaves work and then use his and my computers to simulate real usage. Is there a way to do this on one computer?

 

[JLCantara]

A simple way to do that is to create a second equivalent (to you) user on your PC. You can then, at any time, simulate 2 different users.

What are the 'problems' (error messages)?

 

[ChrisTheIntern]

JL, thanks for the tip!

The errors were from a version about a week ago. When I had DoCmd.GoToRecord , , acNewRec on Form Load. It gave the error " The command or Action GoToRecord is not available now." I believe for this one, it worked with no error for the first person but any subsequent users were locked out of the form with this error.

In my notes, I wrote: maybe try DoCmd.GoToRecord acDataForm, "NameofForm", acNewRec. Or put the code in the On Dirty procedure.

 

[JLCantara]

After every mods, make sure you compact your app. Some times, Access is very misleading in executing a statement that will be rejected after compaction.

Why do you need to execute that DoCmd???

 

[ChrisTheIntern]

I have a formQualityAssuranceReview that is bound to a tableResponses. I would use the Data Entry property but I also have an edit review button(linked to a textbox for ID #) and a subform that just displays records about the 25 most recent reviews from a query. If I set Data Entry to True, I believe my subform does not update and my edit review button does not work.

 

[JLCantara]

Sorry, but your last post is so obscure... Could you attach a snapshot of the app relationships? And one of the form your describing?

 

[ChrisTheIntern]

This is a picture of my form. Users fill out a QA review of each work order.

Sometimes interns "pre-review" a work order before our experts review them. If an expert isn't paying attention to the subform in the attached picture, and tries to create a new review of a work order that already was pre-reviewed, then an error message shows up because work order number is the primary key. Then the expert has to type in the work order in the textbox next to the edit review cbo and then click edit review to see the pre-review results and add his own comments and answers.

Almost all textboxes and listboxes are bound to a field in the tableResponses.

The subform is not linked to anything and it just displays query results of 25 most recent reviews. The query data comes from tableResponses.

 

[ChrisTheIntern]

I apologize for my bad GUI design. This is the first one I've ever made.

 

[JLCantara]

Your making your live very complicated in trying to bypass normal Access features. Your 4 command buttons are useless: use the navigation buttons for the subform! WO in the subform is useless move it to the subform footer and make the footer invisible. For the WO filter combo I suggest something like 'Locate WO' so that it's function is clear...