Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Forms / April 2008

Tip: Looking for answers? Try searching our database.

Access VBA Userform Load problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Hans Perborn - 01 Apr 2008 13:55 GMT
VBA Userforms that work in Excel or Word 2003 cause problems in Access 2003
when the file format is 2002/2003 but not 2000. VBA code line "Load
UserFormName" cause Run Time error 75. Sometimes also Run time error 57:
Device I/O error.
Hans Perborn - 02 Apr 2008 14:36 GMT
> VBA Userforms that work in Excel or Word 2003 cause problems in Access 2003
> when the file format is 2002/2003 but not 2000. VBA code line "Load
> UserFormName" cause Run Time error 75. Sometimes also Run time error 57:
> Device I/O error.

I have now tested a workaround. First convert the database from file format
2000 to 2002/2003. Enter VBE but don't try to load or display the userforms
using code. Now make new userforms using similar names for each old userform.
Open each matching pair of userforms and copy all controls and code from the
old ones to the new. Remove the old userforms and rename the new ones with
the old names. Remember to save the database from time to time, but never
save the old userforms. You will get a saving prompt where you can disselect
the old ones.
This strategy works but still you cannot export the new userforms and then
import them back again to a database in 2002/2003 format. In that case you
will experience the same problems as importing from the original userforms
from Access 2000 file format.
I suppose this was not what microsoft intended with the VBE import/export
functionality. Does anyone know whether this problem affect Access 2007?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.