Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Changing Subform Problem using SourceObject

Status
Not open for further replies.

jmcclain

Programmer
Aug 14, 2002
27
US
Access Guru's,

I have run into a doozy of an issue. I have an application that uses a 'drill-down' like hiearchy to drill through a series of data levels. Each level has its own subform and when the user traverse's to the next level VBA is used to set the source object to the corresponding form.

Here's the code that does it:

Forms!frmAttrAll!frmAttrSub.SourceObject = "frmAttrL1"

Where frmAttrAll is the main form, frmAttrSub is the subform object on the main form and frmAttrL1 is the form that needs to be assigned to it.

This drill down hierarchy works perfectly on 99% of the computers that we've installed it on, but in a few instances it doesn't work.

Here's the weird part. The user can get through levels 1 and 2, but when they try to go to level 3, the subform doesn't load. I put in a quick workaround to jump to level 4 function (to bypass level 3) and the remaining levels work.

Here's another weird part, we re-imaged a test machine with the particular specs of the non-working PCs and it works fine. The particular specs are Win2000 Professional with Access 2000 SP1. Even with the same specs, we can't get it to work on the users PCs.

I've done a compile on these machines to make sure that everything is all right and this problem still remains.

Any ideas???
 
Is there anything that makes the Level3 form different than the ones for levels 1,2 and 4?

Here's the way I see it. If two machines are running the same chunk of code (e.g. a net based MDB file) and it works on one but not the other, it's a hardware/software problem on the machine that barfs.

Are both machines ALIKE in terms of Office SPs and all?

Are both machines running same level of OS?

If the code works as desired on at least ONE machine, then it works, period. The breakage is NOT in your MDB file.

Now when you say "it doesn't work", do you get an error message? A freeze up? Nothing apparent?

Does the USER whose logged in make any difference? In other words, could the machines where it doesn't work have users who, for some reason, can't perform the operations necessary for the Level 3 form to appear? Since you mention what appear to be a number of PCs running the app, could a user's rights be the problem?

Hmmmm...[hammer]

Jim





Me? Ambivalent? Well, yes and no....
Another free Access forum:
More Access stuff at
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top