VBA problem between 97 and 2000 runtimes. 
Author Message
 VBA problem between 97 and 2000 runtimes.

We are converting our Access 97 databases to Access 2000 and most are going
ok but when we create a runtime version using the new package and deployment
wizard, it creates fine and installs fine but any database with modules seem
to be a problem.  As soon as it goes to run the code, it halts.  It works
fine on pc's with the full version on access, just the runtime version does
not seem to support the VB.  Is there an option we are missing?   Thanks,
Joe


Tue, 02 Apr 2002 03:00:00 GMT  
 VBA problem between 97 and 2000 runtimes.

Quote:
> We are converting our Access 97 databases to Access 2000 and most are going
> ok but when we create a runtime version using the new package and deployment
> wizard, it creates fine and installs fine but any database with modules seem
> to be a problem.  As soon as it goes to run the code, it halts.  It works
> fine on pc's with the full version on access, just the runtime version does
> not seem to support the VB.  Is there an option we are missing?   Thanks,

Declare db as DAO.Database or rs as DAO.Recordset and so on...

Guenther

http://www.ostfrieslandweb.de/



Tue, 02 Apr 2002 03:00:00 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. Access 97 VBA Problem with Windows 2000

2. Compatibility Problem Using MS Excel 97 VBA on Excel 2000/XP - Causes crashes

3. vba problem word 97 and not word 2000

4. convert vba 2000 to vba 97

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

6. Excel 97 VBA vs Excel 2000 VBA

7. VBA 97 vs VBA 2000

8. Using Runtime Access 2000 And Full Ver Access 97 Same CPU Same Time

9. Access 2000 Runtime and Word 97

10. Failure starting Access runtime 97 with Office 2000

11. Runtime Access 2000 and Office 97

12. distributing an app written in access 2000 runtime but client still uses access 97

 

 
Powered by phpBB® Forum Software