Microsoft Access 2002 (XP) Forum

Hello everybody,
my name is Alexandros, I'm the new advocate for Access XP. Once I get settled here, I'll post the installation procedure that made Access XP for me work (Screenshots will follow, in the screenshot section), so please be patient with your questions for a couple of days, till all is posted.

greetings
Alexandros

I did some beta testing of version 3 a while ago.

First time around I got Access XP installed and working relatively well. There were some very annoying display glitches - eg constant flickering in datasheet mode which made the CPU usage rise to 100% ( to redraw the flickering I assume ).

More worrying, however, was that even with small databases with only linked tables, the MDB shell ( the access database file ) would become corrupted quite quickly. It's get cryptic errors about broken indexes and missing objects in the Access system tables. This usually only occured when I was using the developer build to edit databases ( ie forms / reports / queries ).

I also had problems with reports. Any reports that produced more than a few pages of output would exit with an 'out of memory' error.

I successfully installed the 'runtime' version of Access XP on one PC and ran it without major hassles for a couple of days ( reports still didn't work ). The 'runtime' version is a stripped-down version that only allows forms / reports to be run ( VB code included ) but you can't edit the MDB files in any way. When you buy the developer version of Access you get a license to distribute as many of these 'runtime' version as you want. This is why I was investigating it - for deployment here.

Unfortunately in the last beta version of crossover I ran ( which was admittedly quite a while ago ) there was a regression that prevented me from installing the MyODBC ( MySQL ODBC ) driver - which previously was working flawlessly.

Access XP under crossover ( last time I checked ) was WAY too unstable for any serious development. I had to revert to backups on a large number of occasions after my MDB files became corrupt. But the runtime version looked promising. It seems like as long as you don't edit the MDB files, it's relatively stable.

Hi,
first of all, thanks for the feedback, is good to know where it "hurts".
I have published on the my last post the install procedure for CX3.0 that was brought the most stable results for me. It would be helpfull to know
if your databases work better after following that procedure for the CX installation. (Including SP3 for Office XP once that is installed)