Systems is going to start this conversion in a few months. I'm the only vfp developer, but there are a number of Access & Excel devs as well. Are there any obvious (or not so obvious) gotchas?
I realize that the list has been discussing this for some time, but, pigheaded slug that I am, I don't pay any attention until I've actually got to deal with it.
Lew
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Lew,
Just a few pointers.
1. Permissions will probably be your biggest problem if you store or try to store data in the "Program Files" folder. Ideally set up the application program and its associated data if any in its own folder off the root.
2. The dreaded user access control which keeps on prompting if you run the VFP program off a network share. Not difficult to remove if you place the network share in the trusted zone in Internet explorer....this is not immediately obvious!
3. Opening DBC's on network shares for some reason seems to take an absolute age (VFP9) compared with XP. This, you will propbably find, is down to the anti-virus, so you should exclude dbf, fpt, cdx, dbc, dct, dcx file types from being scanned on opening. This will only help but not completely cure the problem.
4. In development mode if you run VFP with administrator privileges and use OLE Drag/Drop within your application then this WILL NOT WORK!! To sort the problem then just run VFP development in standard mode.
5. The VFP Taskpane will not work without an update of Microsoft XML and the VFP9 Soap toolkit.
6. If you use any registered ActiveX controls (.OCX) then make sure you register them using the command line but with admin privileges i.e open up the command prompt as administrator.
Other than that off the top of my head I can't think of anything else. If and when I do I'll let you know.
Dave
-----Original Message-----
From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On Behalf Of Lew
Sent: 06 April 2011 17:01
To: profox@leafe.com
Subject: Windows 7/Office 2010 rollout
Systems is going to start this conversion in a few months. I'm the only vfp developer, but there are a number of Access & Excel devs as well. Are there any obvious (or not so obvious) gotchas?
I realize that the list has been discussing this for some time, but, pigheaded slug that I am, I don't pay any attention until I've actually got to deal with it.
Lew
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/BD031ECABF2B60499200AAB3DBB4A99904E158@EX-A-FPL.FPL.LOCAL
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Oh yes, and if you haven't already done so then switch to Innosetup as opposed to the VFP Microsoft installer.
Dave
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/BD031ECABF2B60499200AAB3DBB4A99904E16A@EX-A-FPL.FPL.LOCAL
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Wed, April 6, 2011 12:01 pm, Lew wrote:
> Systems is going to start this conversion in a few months. I'm the only
> vfp developer, but there are a number of Access & Excel devs as well. Are
> there any obvious (or not so obvious) gotchas?
> I realize that the list has been discussing this for some time, but,
> pigheaded slug that I am, I don't pay any attention until I've actually
> got to deal with it.
> Lew
>
If you're not using VFP 9 SP 2, you'll have some UI issues to deal with.
Dave covered many issues I've dealt with.
This isn't Windows 7 specific.
If you use a loader application that downloads updated EXE's to a local
workstation. You might run into trouble when a different user logs into
the machine and runs when an update is needed. The way to avoid this is to
create the folder where you copy the local EXE to giving it Modify access
to Authenticated Users, maybe Users.
Tracy
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/24829.68.143.253.178.1302147655.squirrel@powerchurch.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Tracy,
Regarding your statement
"..create the folder where you copy the local EXE to giving it
Modify access to Authenticated Users..."
Would this be done (and if so, how) by the Innosetup program during
installation? So far, I've had to set this folder attribute manually.
Mike Copeland
> On Wed, April 6, 2011 12:01 pm, Lew wrote:
>> Systems is going to start this conversion in a few months. I'm the only
>> vfp developer, but there are a number of Access& Excel devs as well. Are
>> there any obvious (or not so obvious) gotchas?
>> I realize that the list has been discussing this for some time, but,
>> pigheaded slug that I am, I don't pay any attention until I've actually
>> got to deal with it.
>> Lew
>>
> If you're not using VFP 9 SP 2, you'll have some UI issues to deal with.
> Dave covered many issues I've dealt with.
>
> This isn't Windows 7 specific.
> If you use a loader application that downloads updated EXE's to a local
> workstation. You might run into trouble when a different user logs into
> the machine and runs when an update is needed. The way to avoid this is to
> create the folder where you copy the local EXE to giving it Modify access
> to Authenticated Users, maybe Users.
>
> Tracy
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4D9D3F79.2020700@ggisoft.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Hi - yes, Innosetup can do it.
On Thu, Apr 7, 2011 at 7:37 AM, Mike Copeland <mlcopeland@gmail.com> wrote:
> Tracy,
>
> Regarding your statement
> "..create the folder where you copy the local EXE to giving it
> Modify access to Authenticated Users..."
>
> Would this be done (and if so, how) by the Innosetup program during
> installation? So far, I've had to set this folder attribute manually.
>
> Mike Copeland
>
>> On Wed, April 6, 2011 12:01 pm, Lew wrote:
>>> Systems is going to start this conversion in a few months. I'm the only
>>> vfp developer, but there are a number of Access& Excel devs as well. Are
>>> there any obvious (or not so obvious) gotchas?
>>> I realize that the list has been discussing this for some time, but,
>>> pigheaded slug that I am, I don't pay any attention until I've actually
>>> got to deal with it.
>>> Lew
>>>
>> If you're not using VFP 9 SP 2, you'll have some UI issues to deal with.
>> Dave covered many issues I've dealt with.
>>
>> This isn't Windows 7 specific.
>> If you use a loader application that downloads updated EXE's to a local
>> workstation. You might run into trouble when a different user logs into
>> the machine and runs when an update is needed. The way to avoid this is to
>> create the folder where you copy the local EXE to giving it Modify access
>> to Authenticated Users, maybe Users.
>>
>> Tracy
>>
>>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/BANLkTi=fUOGb99qS3Y2meBf8dfLa0jLDDg@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Wed, 06 Apr 2011 16:14 +0000, "Dave Crozier"
<DCrozier@flexipol.co.uk> wrote:
> 3. Opening DBC's on network shares for some reason seems to take an
> absolute age (VFP9) compared with XP. This, you will propbably find, is
> down to the anti-virus, so you should exclude dbf, fpt, cdx, dbc, dct,
> dcx file types from being scanned on opening. This will only help but not
> completely cure the problem.
Just on that one ... I work for a company that sells a large VFP9
application that is installed on thousands of customer sites. This
application has EXE and support files on the client PCs and other
metadata and actual data accessed over UNC shares. It basically uses
hundreds of DBF files.
Customers have recently started upgrading to Windows 7, 64-bit in most
cases. Quite a few were complaining that the brand new Windows 7
machines were considerably slower than even really old XP boxes when
using this app. Like taking two minutes to log in, in extreme cases.
In almost every case we have found this to be down to network card
drivers and settings. The one change that I have found makes a huge
difference is what is called 'Interrupt Moderation' on Intel cards, and
a similar name on Broadcom and Realtek. This will be 'on' by default,
and is intended to reduce CPU load by batching network requests and then
generating one interrupt to send them, rather than one interrupt per
request. However with things like our application it has the opposite
effect. Turning it 'off' is a night-and-day difference in speed.
The other thing I would say is - ensure that the Windows 7 and Server
2008 if applicable are on the latest service pack, as this removes the
problem where you have to turn off SMB2 to stop VFP index corruption.
Oh, and make sure it's Office 32-bit, not Office 64-bit.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1302163059.25473.1438416621@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Alan,
Nice find. I did the same with a few of our PC's and id does make a dramatic difference when opening tables for browsing in grids.
Thanks
Dave C
-----Original Message-----
From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On Behalf Of Alan Bourke
Sent: 07 April 2011 08:58
To: profox@leafe.com
Subject: RE: Windows 7/Office 2010 rollout
On Wed, 06 Apr 2011 16:14 +0000, "Dave Crozier"
<DCrozier@flexipol.co.uk> wrote:
> 3. Opening DBC's on network shares for some reason seems to take an
> absolute age (VFP9) compared with XP. This, you will propbably find, is
> down to the anti-virus, so you should exclude dbf, fpt, cdx, dbc, dct,
> dcx file types from being scanned on opening. This will only help but not
> completely cure the problem.
Just on that one ... I work for a company that sells a large VFP9
application that is installed on thousands of customer sites. This
application has EXE and support files on the client PCs and other
metadata and actual data accessed over UNC shares. It basically uses
hundreds of DBF files.
Customers have recently started upgrading to Windows 7, 64-bit in most
cases. Quite a few were complaining that the brand new Windows 7
machines were considerably slower than even really old XP boxes when
using this app. Like taking two minutes to log in, in extreme cases.
In almost every case we have found this to be down to network card
drivers and settings. The one change that I have found makes a huge
difference is what is called 'Interrupt Moderation' on Intel cards, and
a similar name on Broadcom and Realtek. This will be 'on' by default,
and is intended to reduce CPU load by batching network requests and then
generating one interrupt to send them, rather than one interrupt per
request. However with things like our application it has the opposite
effect. Turning it 'off' is a night-and-day difference in speed.
The other thing I would say is - ensure that the Windows 7 and Server
2008 if applicable are on the latest service pack, as this removes the
problem where you have to turn off SMB2 to stop VFP index corruption.
Oh, and make sure it's Office 32-bit, not Office 64-bit.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/BD031ECABF2B60499200AAB3DBB4A99904E387@EX-A-FPL.FPL.LOCAL
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Mike Copeland wrote on 2011-04-07:
> Tracy,
>
> Regarding your statement
> "..create the folder where you copy the local EXE to giving it
> Modify access to Authenticated Users..."
>
> Would this be done (and if so, how) by the Innosetup program during
> installation? So far, I've had to set this folder attribute manually.
>
> Mike Copeland
Mike,
These are the line currently used in the Inno script. ProcIsRemote is a
procedure in the script to determine if this is running on a local drive.
When it is, there is no reason to create the folder.
[Dirs]
Name: "{commonappdata}\PowerChurch"; Check: ProcIsRemote; Permissions:
authusers-modify
Tracy Pearson
PowerChurch Software
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/001301cbf52e$a7ce3180$f76a9480$@com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
How about ocx/activeX/dll issues?
Some of our developers will be on W7 machines and still deploying to
XP machines & vice versa. Other W7 developed apps will reside on our
W2003 server.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/BANLkTikz=TrVA0t38+fcBaM__geqYo109Q@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.