the vba in the database is corrupt

[vinc]

i have an access application on a server ,when accessing it from some new
locations (desktops) using the same version of access (XP), an error occured
: "the visual basic for application in the database is corrupt". but i still
accessing it from many other desktops without errors. what is the
problem???!!!!

 

[S.Clark]

Best practice is to put a front end .mdb on each local computer, linked to a
backend .mdb on the network. It sounds like you have only one .mdb on the
network for all users to share. This is going to cause you more problems
than its worth, so even if you fix this issue, you're just biding time until
the next PITA arrives. But, you can try to repair and compact, decompile the
code, or import it into a new .mdb.

 

[Tony Toews [MVP]]

i have an access application on a server ,when accessing it from some new
locations (desktops) using the same version of access (XP), an error occured
: "the visual basic for application in the database is corrupt". but i still
accessing it from many other desktops without errors. what is the
problem???!!!!

Could be that some users have Office XP SP2 installed and others SP3.

You want to split the MDB into a Front End MDB containing the queries,
forms, reports, macros and modules with just the tables and
relationships in the Back End MDB. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
free Auto FE Updater utility at http://www.autofeupdater.com/ to make
the distribution of new FEs relatively painless.. The utility also
supports Terminal Server/Citrix quite nicely.

Tony