Hi All
Hope someone can help out . . .
I have a system that worked fine in A97 .and Win 98 with NT server . . . 10
PCs running a front end MDB and usual backend MDB with tables on the server.
All PCs have identical printer setups pointing to a Xerox and a Canon
printer on the network.
In A97 I would make changes to a local frontend MDB, copy the new version to
the server and then copy the frontend down to each PC. This worked perfectly
well. Over the last few months all the PCs have been upgraded to Windows XP
and Office 2000. Initially the A97 version of the MDB was converted locally
on each PC as it came online. This converted copy worked OK linking to the
tables mdb which stayed as a A97 MDB.
Last week when all PCs had been converted to Win XP / MSO 2K , I converted
the backend to A2K and set everything up in A2k as I had done in A97. Then
proceeded to make some requested design changes . . .
To kick off a clean version of A2K frontend, I created a new MDB and
imported all the forms/reports etc from the original A97 frontend and linked
to the new tables in the new A2K backend. . . I changed the names to denote
the version change.
All this seemed to go OK. However when I copied the new frontend to the
server and then distributed it to the PCs the copied version lost all the
specific printer/margins settings in the reports. . . I tried several times
to fix the margins etc but each time it got loaded back up to the server and
copied down to a PC the settings reverted to the default margins etc . .
and landscape reports became portrait.
If a user changed the settings locally . . they would stick. . . this loss
of settings even occured with an MDE version of the frontend.
After a few new versions were distributed some PCs began to shut down Access
when trying to display a certain reports. .
The shutdown did not occur on a laptop running MSO XP on a Win XP OS.
This bizzare behaviour with corrupting MDBs was one reason I stayed clear of
MSA 2k back in 2000 but I now have to deal with it for this client . . . and
I also downloaded ther latest jet 4.0 patchs from MS website . . but this
didnt solve the problem . .
This flakey behaviour of MSA 2k is a real pain . . so can anyone shed some
light . . I dont think the client is ready to pay even MORE money to
upgrade to MSA XP after shelling out a bundle to go from A97 to A2k which
the did they did back in 2000 and then went back to A97 because of A2k
performance problems . .
cheers and TIA for any helpfull sugestions . . getting very frustrated here
.. .
Paul G
Hope someone can help out . . .
I have a system that worked fine in A97 .and Win 98 with NT server . . . 10
PCs running a front end MDB and usual backend MDB with tables on the server.
All PCs have identical printer setups pointing to a Xerox and a Canon
printer on the network.
In A97 I would make changes to a local frontend MDB, copy the new version to
the server and then copy the frontend down to each PC. This worked perfectly
well. Over the last few months all the PCs have been upgraded to Windows XP
and Office 2000. Initially the A97 version of the MDB was converted locally
on each PC as it came online. This converted copy worked OK linking to the
tables mdb which stayed as a A97 MDB.
Last week when all PCs had been converted to Win XP / MSO 2K , I converted
the backend to A2K and set everything up in A2k as I had done in A97. Then
proceeded to make some requested design changes . . .
To kick off a clean version of A2K frontend, I created a new MDB and
imported all the forms/reports etc from the original A97 frontend and linked
to the new tables in the new A2K backend. . . I changed the names to denote
the version change.
All this seemed to go OK. However when I copied the new frontend to the
server and then distributed it to the PCs the copied version lost all the
specific printer/margins settings in the reports. . . I tried several times
to fix the margins etc but each time it got loaded back up to the server and
copied down to a PC the settings reverted to the default margins etc . .
and landscape reports became portrait.
If a user changed the settings locally . . they would stick. . . this loss
of settings even occured with an MDE version of the frontend.
After a few new versions were distributed some PCs began to shut down Access
when trying to display a certain reports. .
The shutdown did not occur on a laptop running MSO XP on a Win XP OS.
This bizzare behaviour with corrupting MDBs was one reason I stayed clear of
MSA 2k back in 2000 but I now have to deal with it for this client . . . and
I also downloaded ther latest jet 4.0 patchs from MS website . . but this
didnt solve the problem . .
This flakey behaviour of MSA 2k is a real pain . . so can anyone shed some
light . . I dont think the client is ready to pay even MORE money to
upgrade to MSA XP after shelling out a bundle to go from A97 to A2k which
the did they did back in 2000 and then went back to A97 because of A2k
performance problems . .
cheers and TIA for any helpfull sugestions . . getting very frustrated here
.. .
Paul G
Comment