Karen Schaefer
asked on
Problem between Access 2003 & Access 2007 displaying forms correctly
I am in the process of validating my Access 2003 database and the functionality working in the new Access 2007 environment w/o converting to 2007 - will have mixed usage for awhile.
The forms within the AK3 version work perfectly, however not in Ak7. When I open the form with the multiple subforms in AK3 if functions correctly, but for some reason when the same form/subforms open in AK7 the subform (datasheet view) will only display 1 record when it should be multiple records. When I view this subform outside of the Main form/Subform it displays the data correctly. The Query returns the correct records etc.
Does anyone know why this is happening?
The forms within the AK3 version work perfectly, however not in Ak7. When I open the form with the multiple subforms in AK3 if functions correctly, but for some reason when the same form/subforms open in AK7 the subform (datasheet view) will only display 1 record when it should be multiple records. When I view this subform outside of the Main form/Subform it displays the data correctly. The Query returns the correct records etc.
Does anyone know why this is happening?
ASKER
how to I set the specific VBA code in the Trusted center? the link does not show how to link the VBA code.
K
K
Umm.... Link the VBA code? Not sure what you mean.
You either trust the location with the current database or move the data to a folder that is aset as a trusted location. Nothing to "link"
Is the database in a folder that Access 2007 thinks is a trusted location (folder)?
You either trust the location with the current database or move the data to a folder that is aset as a trusted location. Nothing to "link"
Is the database in a folder that Access 2007 thinks is a trusted location (folder)?
ASKER
Yes, the drive I am using is in the trusted center and I am still having the issue with the form - any other ideas.
Don't know if this makes a difference the database is split - but both are on the same drive.
K
Don't know if this makes a difference the database is split - but both are on the same drive.
K
Same drive?e they both in a trusted location?
Is the front end on the local hard drive in a trusted location?
To be sure the VBA code is enabled, does other VBA code work in the front end?
Do you have the Office 2007 SP2 update installed?
Is the front end on the local hard drive in a trusted location?
To be sure the VBA code is enabled, does other VBA code work in the front end?
Do you have the Office 2007 SP2 update installed?
ASKER
Yes they are both on the same drive - that I am calling Dev Drive.
Yes all other code seems to be functioning correctly -
It seems to be just this form/subform that is causing the problems.
Where do I check for the version in Ak7 - don't see the about Access info?
Yes all other code seems to be functioning correctly -
It seems to be just this form/subform that is causing the problems.
Where do I check for the version in Ak7 - don't see the about Access info?
ASKER
found it. see attached
AccessServicePack.png
AccessServicePack.png
Got all your updates installed... (For Windows as well as Office?)?
If it only displays 1 record, is it always the first one?
Do you Compact the DB regularly?
Have you tried converting the DB to the 2007 format?
(When I open the form with the multiple subforms)
How many subforms are we talking about here?
Are you linking them with the standard Master/child linking field properties?
JeffCoachman
If it only displays 1 record, is it always the first one?
Do you Compact the DB regularly?
Have you tried converting the DB to the 2007 format?
(When I open the form with the multiple subforms)
How many subforms are we talking about here?
Are you linking them with the standard Master/child linking field properties?
JeffCoachman
ASKER
Jeff,
Got all your updates installed... (For Windows as well as Office?)? YES
If it only displays 1 record, is it always the first one? NO - the last record previously selected usually.
Do you Compact the DB regularly? YES
Have you tried converting the DB to the 2007 format? - Can't convert - still need to be able to use it in previous versions
(When I open the form with the multiple subforms)
How many subforms are we talking about here? 2- where I am setting the sourceobject via vba code
Are you linking them with the standard Master/child linking field properties? NO since the vba code
thanks,
Karen
Got all your updates installed... (For Windows as well as Office?)? YES
If it only displays 1 record, is it always the first one? NO - the last record previously selected usually.
Do you Compact the DB regularly? YES
Have you tried converting the DB to the 2007 format? - Can't convert - still need to be able to use it in previous versions
(When I open the form with the multiple subforms)
How many subforms are we talking about here? 2- where I am setting the sourceobject via vba code
Are you linking them with the standard Master/child linking field properties? NO since the vba code
thanks,
Karen
ASKER
I am currently in the process of creating a sample mdb with test data - but its not as easy as 1 thinks - may take several hours to change the data around.
k
k
ASKER
Well I converted a copy to Ak7 and still have the same issue with the subform only displaying the last record selected.
There isn't a criteria on the query that would limit the data, there isn't a limit on the form/subform to limit the data - I am really stumped by this. All my research has not turned up any solution.
Come on guys - put your heads together - or have I stumped you!
Karen
There isn't a criteria on the query that would limit the data, there isn't a limit on the form/subform to limit the data - I am really stumped by this. All my research has not turned up any solution.
Come on guys - put your heads together - or have I stumped you!
Karen
Karen,
If it were my database I would:
1) create a new blank MDB with Access 2003.
2) Create all the linked tables.
3) Import all the object from the existing front end except for the linked tables.
If it were my database I would:
1) create a new blank MDB with Access 2003.
2) Create all the linked tables.
3) Import all the object from the existing front end except for the linked tables.
ASKER
tried that, didn't make a differences the subform still only displays last record selected - it acts like it is retaining the last record id and opening the subform to that - but that is not possible since there is not a variable to hold that value.
Thanks,
Karen
Thanks,
Karen
But there is a form property that can hold it.
For sub form's form properties, have you checked the on the data tab to be sure there is not a filter or anything else tath might cause it?
For sub form's form properties, have you checked the on the data tab to be sure there is not a filter or anything else tath might cause it?
Let's start over.
You have a main form (frmMain) and a subform (fsubBuggy). When you open fsubBuggy, it shows “all” records. When you open frmMain, you set the source object of a subform object (subDetail) to display fsubBuggy, via VBA. In that case, Access 2003 shows “all” records, but Access 2007 (opening the same database) shows only one.
Is that about right?
Create a new form, frmTest, showing fsubBuggy immediately (via properties). Works? Clear the source object and run code similar to frmMain to display it. Works? Make a copy of the main form frmCopy. Remove the VBA module entirely, set fsubBuggy via properties. Works? Clear property and reinstall only the code setting the source object... At some point the bug should reappear, that will be the step to examine.
Please show us the code you use to load fsubBuggy, and explain why you need VBA at all for this. Check the link master/child properties (they can exist even when you set the source object through code). You speak about two subforms. Are you loading two instances of frmBuggy?
(°v°)
You have a main form (frmMain) and a subform (fsubBuggy). When you open fsubBuggy, it shows “all” records. When you open frmMain, you set the source object of a subform object (subDetail) to display fsubBuggy, via VBA. In that case, Access 2003 shows “all” records, but Access 2007 (opening the same database) shows only one.
Is that about right?
Create a new form, frmTest, showing fsubBuggy immediately (via properties). Works? Clear the source object and run code similar to frmMain to display it. Works? Make a copy of the main form frmCopy. Remove the VBA module entirely, set fsubBuggy via properties. Works? Clear property and reinstall only the code setting the source object... At some point the bug should reappear, that will be the step to examine.
Please show us the code you use to load fsubBuggy, and explain why you need VBA at all for this. Check the link master/child properties (they can exist even when you set the source object through code). You speak about two subforms. Are you loading two instances of frmBuggy?
(°v°)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
found solution elsewhere.
WOW. No wounder you stumped the Experts.
I normally don't change the record source of a form.. I edit the queryDef(). That may explain why I have not run into this before.
Thank you for sharing the solution!
I normally don't change the record source of a form.. I edit the queryDef(). That may explain why I have not run into this before.
Thank you for sharing the solution!
> or have I stumped you!
Jeff asked you to check the link fields, you didn't. I asked you again... specifically to check for this behaviour... you didn't answer...
Anyway, I'm glad you found your solution.
(°v°)
Jeff asked you to check the link fields, you didn't. I asked you again... specifically to check for this behaviour... you didn't answer...
Anyway, I'm glad you found your solution.
(°v°)
If yes then you must make sure thst you trust teh VBA code.
See: Trust Center in Access 2007 and 2010