Search results

I just run my merge code again and it worked. To be honest I really don't understand what the above message meant, what Server and why was not referring to properly. Anyway, it works and that's the main thing - this is great. Thank you Paul for your suggestions and support.

Well, I followed the links. I am trying to register both dlls as below: 1. Coped both dll to "C:\Windows\SysWOW64" folder 2. In command line running the following: "C:\Windows\SysWOW64\regsvr32 C:\Windows\SysWOW64\dynapdf.dll" Getting the following error: "The module...

My theory was wrong, please ignore it. I've just tested with 2 PDF files created with completely different PDF driver and it worked on XP machine with Access 2003. It must be something to do with 64 bits Windows, but I did try to have the dlls in all three folders. I don't know if this helps...

Yes, I know. I have copied the 2 dll files in all 3 places, In current .mdb file folder, system32 folder and in SysWOW64. Unfortunately I am getting the same error. I am not sure if this can cause the problem. In new Access 2013 I am using built-in function to convert to PDF and then having...

It was so long ago, but I believe this is where I've downloaded the code example: http://www.lebans.com/reporttopdf.htm

Hi, we are moving from Access 2003 to 2013 using Windows 8.1 64bits. We used Leban's code and library to create and merge pdfs. C Creating pdfs can be done with built-in functionality in Access 2013. But I can't find a way of merging pdfs. I've tried Leban's Dlls files but I am getting...

I finally found the solution, which involves changing the Sandbox value from 3 to 2 but in a different registry location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Access Connectivity Engine\Engines That's it. Thanks for your replies.

Re: Runnding .mdb 2003 file in Access 2010 Yes, the database is .mdb file. Unfortunately we currently can't upgrade to .accdb version as most users still use Access 2003 on their XP machines. As to upgrading to potentially new machines and OSs - I personally like the idea very much, but...

Re: Runnding .mdb 2003 file in Access 2010 Thanks for your reply Paul. I don't know exactly what you meant by linking the master and child. Is this selecting master/child fields on both forms? If yes, then that shouldn't be the case because the file is used by other users as well. Also I...

Hi, We are experiencing the problem with running Access 2003 .mdb file on Access 2010 on XP, it works fine in Access 2003 and even in 2007. The application works, but few subforms displaying blank with white background. Has anyone experienced this problem before ?

Hi, I've got this problem which I can't figure out the cause. I have a report in Access which is printed through VBA. The VBA code, prior to print, sets the application printer, then prints out. All these works fine on my local machine. But once I login to another machine on a network...

Thanks, I haven't had a change to replace a driver, but will post back when this is resolved. Thanks again

Have you tried in your macro print code instead of say: DoCmd.printout Replace with DoCmd.printout acPages, 1, 1

Yes, I would need to start googling again. I've posted on HP support forum yesterday and no replies yet on there. So I will just do general searches now. Thanks again for your replies.

This is weird. I just tried to print in Word doc and failed. It does so in Access with manual printing though. Any ideas please ?

Thanks for your reply, do you mean print word document manually ? As I don't have a vba code in Word.

Hi, I am having problem with printing in duplex with HP printer: "HP LaserJet P4010_P4510 Series PCL 6" programmatically using VBA. I can print duplex on a different printer ie "Brother" made, but not with HP. Because of this I am thinking it must to do with HP printer driver than my VBA...

Thank you Bob, I will try that first.

I see, is this means that if I change the source in the DSN in the Windows ODBC Manager from 1 to 2, then I have to refresh the linked tables as well. If this is the case then it explains why I was still pointing to the same SQL instance after changing from one DSN name to another. Because so...

Ok, these are the steps I am going through. Checking first the system table. Say there is a row for today. I am connected to remote SQL Server. Then closing Access, going to ODBC connection administrator, changing manually a connection to reference now to local SQL Server. Then open Access...