Recent content by justphilip

I checked to see what I now have: MS Office Pro | Access version: 14.0.7180.5002 (64-bit). Thanks for the tip! I fixed my module modOpenSaveFile problem. To tell the truth, this db module was incorporated back around 1997 when I found it on the internet and I've forgotten exactly what it did...

Thanks all for the great responses! To correct my poor typing, I am currently using MS Office 2010 - Access 2010 in I believe 32-bit mode. All of my databases were developed on older platforms going as far back as 1995. The problems occurred in module modOpenSaveFile, code originally written by...

I am new to VB Studio and I've done something and I do not know how to get out of it. When I click on the DEBUG Tab to run start debug I end up with a series of error messages like the ones below: Severity Code Description Project File Line Suppression State Error Unable to copy file...

Thanks for the response. I don't think my problem is with MS Access, I've been using it since Win 95! I am very new to VB Studio, however and I'm having problems getting started in that environment. JP

I am puzzled by my VB Studio 2015 not testing my current Form; it is using the form that existed before I changed/added buttons! I saved the altered form with lock on and off - no change! I can't see anything in the Form properties that could cause this. It's got to be something simple! TIA JP...

Happy Days! I was advised to forget the VB PowerPacks, at least until MS provides support if ever! I did manage to find "PrintForm" while familiarizing myself with VB Studio. Go to top ribbon and select Tools > Choose Toolbox Items > PrintForm Now if only I could relocate the location where...

In a 64-bit total system environment using Visual Basic Studio Community 2015 Software, is it possible to obtain a compatible Visual Basic PowerPack module/dll that won't issue a critical overwrite error when installed? TIA JP :banghead:

Thank you for your response. I placed my cursor on my form and then pressed Alt+Ctrl+X; my cursor moved to the Toolbox list. No Visual Basic PowerPack appeared in the list of tools in any catgory in the Toollbox. I also did another install/repair of the downloaded vb-vbpowerpacks (1,012KB).

Thanks for responding to my query. The Toolbox under “All Windows Forms” tab has the following listed: PrintDialog, PrintDocument, PrintPreviewControl and PrintPreviewDialog. No PrintForm component is listed nor a header for Visual Basic PowerPacks.

I am attempting to improve my VB programing skills using the textbook "Programming in Visual Basic 2010," by Julia Case Bradley & Anita C. Millspaugh. I am using VB Studio 2015 Community to do my lessons in a total 64-bit environment. My current lesson (pg. 40) calls for using "PrintForm"...

I am attempting to improve my VB programing skills using the textbook "Programming in Visual Basic 2010," by Julia Case Bradley & Anita C. Millspaugh. The lessons eventually cover Visual Studio and .NET. I am currently using Access 2010 and am in a total 64-bit environment. Question...

Am I done? The #if logic fixed the problems but the #else logic shows up with compiler errors in the 64-bit environment. The #else logic worked in the 32-bit environment, so am I as far as one can go? If not, what topic would be best to research? TIA #if Win64 then Declare PtrSafe Function...

I am a 77 year non techie who had this software installed, being ignorant of the Access consequences, I opted for 64-bit. I started this Access program under Win 95 and have progressed through all of the software changes to the present time. Then there are the possible pit falls of reversal in...

I am definitely running the 64-bit Office Pro with Access at 14.0.7173.5000 (64-bit)

How does one define success? I made the following changes in global module "modOpenSaveFile" and it works for 64-bit platform but the old 32-bit logic( in #else clause) is still red - compiler error. The previous run errors have not reoccurred again! #if Win64 then Declare PtrSafe Function...