By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,395 Members | 1,398 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,395 IT Pros & Developers. It's quick & easy.

A2K help- Why does compact/repair corrupt front end on one server but not another?

P: n/a
Would appreciate any help on this:

I have an A2K frontend/backend application developed & tested on
client's "usual" server. Then moved both back and front ends to a
different server so application could be used by folks in another

Weird behavior: When we put the back-end on the different server,
then we can't do a compact/repair on the front end, no matter where
the front end is (C drive of a PC, new server or old server). The
front end corrupts and loses all the forms, reports, etc.

Of course, the simple solution is never to compact/repair the front
end. But sooner or later, one of the users is going to try this
(they're smarter than the average bear). Not to mention what might
happen if someone compacts/repairs the backend.

I've checked the mso40.dll files, and servers and PCs all have the
same version.

Any ideas?

Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.