Access 97 VBA Problem with Windows 2000 
Author Message
 Access 97 VBA Problem with Windows 2000

Several times when I've been running VBA code in Access 97 under Windows
2000, I get a very polite message saying that Access has encountered an
error and will close--which it does, usually leaving me with unsaved
changes. It's happened on two different machines. Access 97 has never done
that to me on Windows 95 or 98. I couldn't find anything in the Knowledge
Base on this problem.


Mon, 27 Sep 2004 03:19:56 GMT  
 Access 97 VBA Problem with Windows 2000
The database is corrupted. If you don't have a backup, try to repair it
(Tools->Database Utilities->Compact and Repair).

Viktor


Quote:
> Several times when I've been running VBA code in Access 97 under Windows
> 2000, I get a very polite message saying that Access has encountered an
> error and will close--which it does, usually leaving me with unsaved
> changes. It's happened on two different machines. Access 97 has never done
> that to me on Windows 95 or 98. I couldn't find anything in the Knowledge
> Base on this problem.



Tue, 28 Sep 2004 00:44:52 GMT  
 Access 97 VBA Problem with Windows 2000
I too have recently started running Access97 under Win2k.  
Prior to Win2k deployment, our folks did some "upgrade
Windows, don't upgrade Office" compatibility testing and
found some Access97 functions were not supported in Win2k.

This function problem happens on a hit or miss basis, with
little info anywhere about how to solve directly (typical
solution is to write new replacement code).  Some things
affected include exports to Excel in VBA, building forms in
VBA, and reformatting dates in VBA. So, you may see failure
when trying to run an unsupported function but not
otherwise.

In my case, I had some unsupported date formatting crop up
that worked under Win95. The solution was under
Tools|References, item "Microsoft Visual Basic for
Applications Extensibility 5.3."

I suspect these other items are available to me due to
having Office2k now versus Office97 before.  If you don't
have Office2k, you may have some recoding ahead.

-Patrick

Quote:
>-----Original Message-----
>Several times when I've been running VBA code in Access 97
under Windows
>2000, I get a very polite message saying that Access has
encountered an
>error and will close--which it does, usually leaving me
with unsaved
>changes. It's happened on two different machines. Access
97 has never done
>that to me on Windows 95 or 98. I couldn't find anything
in the Knowledge
>Base on this problem.

>.



Tue, 28 Sep 2004 06:21:44 GMT  
 Access 97 VBA Problem with Windows 2000
I don't think that's it.  I run the same one on my Win 98
machine and there's no problem.
Quote:
>-----Original Message-----
>The database is corrupted. If you don't have a backup,
try to repair it
>(Tools->Database Utilities->Compact and Repair).

>Viktor



>> Several times when I've been running VBA code in Access
97 under Windows
>> 2000, I get a very polite message saying that Access
has encountered an
>> error and will close--which it does, usually leaving me
with unsaved
>> changes. It's happened on two different machines.

Access 97 has never done
Quote:
>> that to me on Windows 95 or 98. I couldn't find

anything in the Knowledge

- Show quoted text -

Quote:
>> Base on this problem.

>.



Sat, 02 Oct 2004 06:08:18 GMT  
 
 [ 4 post ] 

 Relevant Pages 

1. Access 2000 VBA Handbook vis a vis Access 97 VBA Handbook

2. Problem With VB6 App With Access 97 Backend Running On Windows 2000 Pro

3. Problem With VB6 App With Access 97 Backend Running On Windows 2000 Pro

4. Access 97 VBA modifications not visible in Access 2000

5. Using VBA to Convert Access 2000 database to Access 97

6. vba access 97 -> access 2000

7. VBA OpenDatabase: Access 97 <-> Access 2000

8. Converting Access 97 to Access 2000 via VBA

9. Access 97: VBA-DAO-Access 97 synchronization problem?

10. Access 97 -> Access 2000 VB Scope Problem

11. Access 97 to Access 2000 Problem

12. Converting Access 2000 to 97 using VBA...

 

 
Powered by phpBB® Forum Software