Groups | Search | Server Info | Keyboard shortcuts | Login | Register

Groups > comp.databases.ms-access > #14174

Re: merging pdf files

Show all headers | View raw

On Tuesday, August 4, 2020 at 6:28:05 AM UTC-6, Ron Paii wrote:
> On Monday, August 3, 2020 at 2:59:05 PM UTC-5, Albert Kallal (Access MVP) wrote: 
> > On Monday, August 3, 2020 at 1:18:23 PM UTC-6, Ron Paii wrote: 
> > > It works in Windows 10 but not 8.1 or 7 
> > > Windows 10 added some new environment variables. 
> > > 
> > > DriverData 
> > > FPS_BROWSER_APP_PROFILE_STRING 
> > > FPS_BROWSER_USER_PROFILE_STRING 
> > > HOMEDRIVE 
> > > HOMEPATH 
> > > HOMESHARE 
> > > LOGONSERVER 
> > > 
> > > Any chance nLoader is using one of these? 
> > No, path name and environment stuff should not matter. 
> > it would be that .net 4.0 is not installed. Win 7, and early win 8's don't have that. 
> > They have by default .net 3.5. 
> > 
> > I could/can re-compile with .net 3.5. The problem is the IL merge utility I am using only goes back to 4.0. 
> > 
> > So, I am faced with a choice: 
> > Dump use of IL merge, and you have one more extra .dll. So, in place of 3 .dll's, you have 4. 
> > 
> > I have re-compiled the .dll to 3.5, but the merge routines used .net 4. This "might" work for you. 
> > 
> > Link here: 
> > https://1drv.ms/u/s!Avrwal_LV4qxhphxjbS7y-SNd_42cg?e=sOLSdk 
> > 
> > So, you can try the new download, but I not oh so sure this will work. 
> > 
> > If it does not work? 
> > 
> > Then I think the most compatible, and best chance of having to do zero to the target computers? 
> > 
> > A re-compile to .net 3.5. But I have to DUMP the use of ILmerge. 
> > All this means is that there will be extra .dll you have to deploy. 
> > 
> > From above, you ONLY should need to re-place "Pmerge.dll" in the location that you are testing. 
> > (and you should exit access - you find the .dll is locked if you running code). 
> > 
> > So, try the new Pmerge.dll - if it works, then great. 
> > If not? 
> > Well, then I'll have to include one extra .dll in this. 
> > 
> > In fact, I might as well do that right now. 
> > 
> > So, here is a 100% .net 3.5 version. It is called PdfMerge35 
> > https://1drv.ms/u/s!Avrwal_LV4qxhphyIggu-rUjMGqPOg?e=BYKkpT 
> > 
> > If that last one don't work - then again I could pull the .net version all the way back to 2.0 - that would be on all these machines. 
> > 
> > R 
> > Albert
> .Net installs on test computers 
> Win7: 3.51 
> Win8.1: 3.5 & 4.5 
> Win10: 3.5 & 4.8 
> 
> The 1st new download worked on windows 7 and 10 but not 8.1 
> The 2nd new version did not work on 7 or 8.1 or 10 
> 
> 7 is Access 2010 full 
> 8.1 is Access 2016 full 
> 10 is Access 2016 runtime, I added a form with a button to test. 
> 
> I will try testing on other 8.1 computers later this week and get back to you. 
> 
> Thank you for all your work on this.

Been busy.
I also did some R&D on what is intstalled on those  computers.
However, (double darn!!!).
While I did re-compile Pmerge to .net 3.5?
I FORGOT to re-compile the nloader.dll!
It was at .net 4.5!!!
The MOST wide spread and pre-installed .net seems to be 4.0.
So, I will re-compile both Pmerge and the nloader.dll to .net 4.0
As noted, my VERY bad - since I did not re-compile the nloader. 
As a FYI:
i tend to leave the nloader at the highest possible .net version (4.5, or even 4.72).
The REASON for this is I use the nloader for those accounting interfaces and deployment to customers machines
This approach means can deploy a .net 3.5 ALL THE WAY UP TO 4.7 WITHOUT having to change nloader.
But this means that the target machine will requite 4.5 or 4.7 to be installed. But this has backwards compatibility all the way back to 3.5
(but ONE MUST have ,net 4.7 or 4.5 installed - then I am free to deploy .net .dlls of near any version). So all I do is tell the customer to ensure that later .net is installed on those machines, and then the .net .dll (pmerge or whatever I am using will work).

So, here is a 4.0 version. I am betting this will likely work on all machines. 

So, the testing you done here is VERY valuable to everyone - including me. (it was Monday I was last here in this group).
So, give this version a try:
Pmerge40.zip
I given it a different name. And both  nloader and Pmerge are set to .net 4.0. This version thus out of the box should have the  most wide spread chance of working. I REALLY need to put up a web page for this utility - but I just don't have the time.

So, 
Merge 4.0 link here:
MergePDF40.zip
https://1drv.ms/u/s!Avrwal_LV4qxhphziHQQOAI0Oq2dQQ?e=DUtuon

Try above - I am betting it should work on most machines.  However, there is a also a manifest setting for msaccess.exe, but I'll leave this issue for another day.

So, my BIG WHOPPER mistake was NOT a re-compile of the nloader (I don't usually bother).
So, previous nloaders were ALL 4.5 - that less then ideal.

So, try above. I will write out a web page for this - and will kindly list out the versions it works for.
R
Albert

Back to comp.databases.ms-access | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

merging pdf files internet.shopping@foobox.com - 2020-07-31 06:33 -0700
  Re: merging pdf files samxjones2@gmail.com - 2020-07-31 07:02 -0700
    Re: merging pdf files internet.shopping@foobox.com - 2020-07-31 08:51 -0700
  Re: merging pdf files "Albert Kallal (Access MVP)" <kallal@msn.com> - 2020-08-01 21:40 -0700
    Re: merging pdf files internet.shopping@foobox.com - 2020-08-02 07:49 -0700
      Re: merging pdf files "Albert Kallal (Access MVP)" <kallal@msn.com> - 2020-08-02 09:34 -0700
        Re: merging pdf files "Albert Kallal (Access MVP)" <kallal@msn.com> - 2020-08-02 13:37 -0700
    Re: merging pdf files internet.shopping@foobox.com - 2020-08-03 00:49 -0700
      Re: merging pdf files Ron Paii <ron81pai@gmail.com> - 2020-08-03 06:55 -0700
        Re: merging pdf files Ron Paii <ron81pai@gmail.com> - 2020-08-03 08:02 -0700
          Re: merging pdf files "Albert Kallal (Access MVP)" <kallal@msn.com> - 2020-08-03 09:28 -0700
            Re: merging pdf files Ron Paii <ron81pai@gmail.com> - 2020-08-03 12:18 -0700
              Re: merging pdf files "Albert Kallal (Access MVP)" <kallal@msn.com> - 2020-08-03 12:59 -0700
                Re: merging pdf files Ron Paii <ron81pai@gmail.com> - 2020-08-04 05:28 -0700
                Re: merging pdf files internet.shopping@foobox.com - 2020-08-04 08:48 -0700
                Re: merging pdf files "Albert Kallal (Access MVP)" <kallal@msn.com> - 2020-08-05 10:18 -0700
                Re: merging pdf files lucteunis1@gmail.com - 2021-02-10 12:01 -0800
                Re: merging pdf files "Albert Kallal (Access MVP)" <kallal@msn.com> - 2021-02-11 15:04 -0800
                Re: merging pdf files Keith Tizzard <internet.shopping@foobox.com> - 2021-06-24 08:44 -0700
    Re: merging pdf files musicloverlch <lhowey@gmail.com> - 2021-08-24 09:37 -0700
      Re: merging pdf files Keith Tizzard <internet.shopping@foobox.com> - 2021-08-24 10:42 -0700
        Re: merging pdf files musicloverlch <lhowey@gmail.com> - 2021-08-25 09:23 -0700
          Re: merging pdf files Keith Tizzard <internet.shopping@foobox.com> - 2021-08-25 09:39 -0700
            Re: merging pdf files musicloverlch <lhowey@gmail.com> - 2021-09-10 07:20 -0700
              Re: merging pdf files "Albert Kallal (Access MVP)" <kallal@msn.com> - 2021-11-11 11:09 -0800
                Re: merging pdf files Extreme Estabrooks <jestabrook@winningsolutionsinc.com> - 2021-12-29 08:03 -0800
                Re: merging pdf files Extreme Estabrooks <jestabrook@winningsolutionsinc.com> - 2021-12-29 08:04 -0800
                Re: merging pdf files ANKIT ROY <ankit.aryson@gmail.com> - 2022-03-02 22:47 -0800

csiph-web