fpODBC for Windows moving not working for me this time.

[Walter D Vaughan Jr]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Friday, December 21, 2012 1:26 PM
> To: Walter D Vaughan Jr
> Cc: filePro Mailing List
> Subject: Re: fpODBC for Windows moving not working for me this time.
> 
> On 12/21/2012 1:01 PM, Walter D Vaughan Jr wrote:
> >> -----Original Message-----
> >> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> >> Sent: Friday, December 21, 2012 12:27 PM
> >> To: Walter D Vaughan Jr
> >> Cc: filePro Mailing List
> >> Subject: Re: fpODBC for Windows moving not working for me this time.
> >>
> >> On 12/21/2012 12:05 PM, Walter D Vaughan Jr wrote:
> >> [...]
> >>> I built a virtual XP-SP3 box because the current drive is failing
> >>> rapidly and I need to use this windows version very infrequently,
> >>> but when I need it I *REALLY* need it. I was expecting everything to
> >>> just work, but I keep getting an error:
> >>> *** A filePro Error Has Occurred *** On File:
> >>> C:\fpodbc/fp/lib/licfp.dat lm error: No Licenses found for the
> >>> product.
> >> [...]
> >
> >> What does "licinfo c:/fpodbc/fp/lib/licfp.dat" show?
> >
> > C:\fpodbc>licinfo c:/fpodbc/fp/lib/licfp.dat 'licinfo' is not
> > recognized as an internal or external command, operable program or
> > batch file.
> >
> > I searched the working workstation, it does not appear to be anywhere on
> it.
> > This is pre license manager no?
> > Can I download that .exe somewhere?
> 
> What version of filePro are you using? Since you are getting an error on
the
> license file, I would suspect that you're using a version that uses the
license
> file.  Perhaps the fp directory isn't on PATH, and therefore you need to
either
> be in the fp directory, or give the path on the command line, such as:
> 
>      c:\fpodbc\fp\licinfo c:/fpodbc/fp/lib/licfp.dat

I don't have that executable file with my install of fpODBC v1.0.13D09

But what I do have is a now working instance on my virtual machine.

1) Discovered that I had the read only bit set for the fpODBC folder
	- Had it remove that  and for any contents (duh!)
2) it probably was fixed at that point, but just for laughs through AD I
gave full access to domain users to the fpodbc directory tree

After I did both the above steps I tested filePro and it ran just fine...

Anyone else following this, there are also a few .dll's that are not in the
fpodbc directory structure you have to move as well as setting the volumeID
to what is expected by your original license. 

Happy End of Mayan Calendar Days Everyone!

--
Walter