VBA 7 Reference for use with Access 2010

[clmarks]

I have turned the Microsoft website upside down trying to find the VBA 7 Reference Manual. No luck. Can anyone point me in the right direction?

I have to rebuild our Access database almost completely. None of the buttons, macros, combo-boxes built with 2003 work in 2010. And none of the data validation and automation procedures I wrote in VBA using Access 2003 work.

So far I have been able to re-build many of my buttons by just playing around until I get it figured out. But simple things like getting forms to maximize when they open, or being able to push a button and open a new form with the child records of the parent displayed on the previous screen are really eluding me.

I have ordered books, but they won't be in for two weeks. I really expected most things to work when we upgraded because I did not use the menus in my application.

Any direction or suggestions would be appreciated.

Cherry

 

[boblarson]

VBA 7???? Where did you get that number from?

Also, if you import everything into a new ACCDB file you shouldn't have a problem with code and things working AS LONG as you have put the database in a TRUSTED LOCATION and have set such location to be trusted within Access 2010.

 

[boblarson]

Also, if you want to have me take a look at some of them, you can email them to me and let me know what is not working so I can see if I can spot why.

 

[clmarks]

Hi, Bob,

I got that number from the Microsoft website. I just emailed the guy who takes care of our thin-client network (remotely) this tidbit that I found on there:

VBA settings migration

In Office 2010, Visual Basic for Applications (VBA) 6.0 was updated to VBA 7.0. VBA 7.0 settings were reset to their defaults after migration instead of automatically repopulating. This occurred because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.


Version Registry subkey Office 2000 through Office 2007
HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\6.0\Common
Office 2010
HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\7.0\Common
To correct this problem, copy the VBA 6.0 registry keys from the 6.0 hive to the 7.0 hive.
For more information, see Migrate user data registry keys in Office 2010 and Compatibility Between the 32-bit and 64-bit Versions of Office 2010 (http://go.microsoft.com/fwlink/?LinkId=185841).

Maybe this will help. But at this time absolutely nothing in my database works. When I look at the data in the back end, everyting is fine, but viewing through my data entry forms the data seems to get lost. On the first form I have the client master information and one subform for each of their admissions. They can use a button by each admission line to show the financial information for that admission. They can push a button by each financial record to show exactly what services were provided using that funding source. Obviously the problem is in my forms, but I can't seem to figure out what's happening.

If this hive change works I will be much relieved. I only have about 10 days to get this done.

Thanks, as always, for your help. I have come to rely very much on your input.

Cherry

 

[clmarks]

Also, I'll send the front end and a back end with sample data in the morning. I would be glad to have you take a look at it. I just can't get it together today.

Cherry

 

[clmarks]

Bob, I thought I had taken care of the trust settings, but after reading your message yesteday I went back and took a second look. This time a got a slightly different screen which let me set the specific folder containing the database as a trusted site. Before I had only seen a little check box at the bottom of the screen. I'm going to go back to the Microsoft site and do some reading to make sure that I am setting up the trusted area correctly so as not to be wasting your time.

Thank you again. And, I'll post the results of my efforts.

Cherry

 

[Banana]

The only difference in VBA7 are basically the following:

1) 64-bit support
2) Three new keywords (2 data types and 1 modifier): LongPtr, LongLong and PtrSafe
3) New function: CLngLng() (?)
4) New compilation constants: VBA7 and Win64


All of the changes has to do with supporting 64-bit environment, really. The difference is most drastic when we're dealing with API and in a 64-bit environment. 32-bit API declaration will continue to be backward compatible as long it's running in a 32-bit environment.

 

[clmarks]

Thanks, Banana. I have to admit to being a bit overwhelmed with our going through so many changes at once. I think that this week I just reached the point of being functionally brain dead. I'm just having to slow down an think more slowly.

You guys just can't imagine how much this forum helps me.

Cherry

 

[clmarks]

Bob, apparently the whole problem was that I did not set up the trusted locations correction. Everything works perfectly now. Thank you again.

Cherry

 

[boblarson]

Bob, apparently the whole problem was that I did not set up the trusted locations correction. Everything works perfectly now. Thank you again.

Cherry

Glad you got it worked out. I was really wondering what could be up as I know that I've not had much difficulty in moving between versions for most of my stuff.