Access 2000 -> Access 2002 client glitches

UThomas

Senior member
Apr 18, 2000
251
0
0
One of my users just upgraded from Win95/Access 2k to Win2k/Access 2002. For whatever reason she is now getting glitches in the client mostly around reporting including:

*When going to preview some reports she gets the error "The search key not
found in any record." The knowledge base has one entry on this error and says it has to do with filling a memo field. None of the tables in my database (SQL Server 2k linked tables) contain memo fields. Any help would be apreciated!

*When trying to export a previewed report to excell she gets "Not enough memory" even though the report is only one page long and there are no other open programs (and she has 256 meg ram)

*Some summary fields on the report now show up as "#Name?" and "#Error" when they use to work (and continue to work) on other computers.

Any thoughts/help? I put on all the latest office patches but can't patch Windows 2k b/c of lame corporate restrictions. This is a Access 2k/SQL Server 2k client/server setup, and works fine on a Win95/Access2k and a Win2k/Access2k machine. Just this new Win2k/Access02 doesn't work.

Thomas
 

damiano

Platinum Member
May 29, 2002
2,322
1
0
Originally posted by: UThomas
One of my users just upgraded from Win95/Access 2k to Win2k/Access 2002. For whatever reason she is now getting glitches in the client mostly around reporting including:

*When going to preview some reports she gets the error "The search key not
found in any record." The knowledge base has one entry on this error and says it has to do with filling a memo field. None of the tables in my database (SQL Server 2k linked tables) contain memo fields. Any help would be apreciated!

*When trying to export a previewed report to excell she gets "Not enough memory" even though the report is only one page long and there are no other open programs (and she has 256 meg ram)

*Some summary fields on the report now show up as "#Name?" and "#Error" when they use to work (and continue to work) on other computers.

Any thoughts/help? I put on all the latest office patches but can't patch Windows 2k b/c of lame corporate restrictions. This is a Access 2k/SQL Server 2k client/server setup, and works fine on a Win95/Access2k and a Win2k/Access2k machine. Just this new Win2k/Access02 doesn't work.

Thomas


did you get the problems after changing to sql server
or was your program always with sql server... server?

contact me on aol messenger if you need help I just upgraded a access95 servser / access 95 client system to
sql server 7 / access 2K

and i ran in all these problems.
I may be able to give you a hand

:)
 

UThomas

Senior member
Apr 18, 2000
251
0
0
Dohhh, no AOL IM on my work machine. Anyway, we have been running Access2k with SQL Server 2k for about 4 months now with no problems. And the client continues to run fine on non Access 2002 machines. The only advice I've heard so far is that it is a bug with different service packs of the Jet database engine.

What did you end up doing?

Thomas
 

damiano

Platinum Member
May 29, 2002
2,322
1
0
i went to the VB code, put some debug statements to find the db calls and me.refresh statements that did not work and changed every bug one by one.

God luck with all this ...it's a huge pain :(

cheers

Damiano
 

UThomas

Senior member
Apr 18, 2000
251
0
0
Hmmm... but I don't think they are bugs if they work correctly with Access 2000. For example, if I can preview a 500 page report and export it to excell on a Win95/Access 2k machine and can't with the exact same code in a faster Win2k/Access 2002 machine I would think it would be a bug, since there is no user VBA around the export button on the top menu bar.

Thomas
 

damiano

Platinum Member
May 29, 2002
2,322
1
0
what I am saying is that some "bugs" are specific to some office versions...
As I said I had the same problems when chanign access 95 to access 2K, and the problem was that in access 2K, I had to put me.requery on open of the report...
This is one of the reasons why microsoft tools are so so.. is cuz all new products are different from old ones...
Oh well,
As I said, putting debug statements is how I fixed the problem... and It was a pain in the ass...

Good luck anyways

cheers


Damiano
 

UThomas

Senior member
Apr 18, 2000
251
0
0
What was your syntax like? If I put a me.requery on the On Open event I get an error saying it is not recognized. I also get an error with docmd.refresh when put with the on open event.

Thanks!