1) It's faster if you don't specify the path nor extension. Add any of these (eg. DO prgs\myprog or DO myprog.PRG) it's getting slower.

2) If the file name is a valid FoxPro name (starts with alpha or underscore, followed by up to 127 alphas, digits or underscores) and only uses ANSi codes below 128, it's significantly faster.

3) SET PATH TO can affect performance either way.

4) Performance dramatically depends on the number of files in the SET PROCEDURE line. In fact, the differences in my tests were huge enough that I considered moving all of the code in AFP into one PRG file when building the project instead of having one PRG files for every class, basically.

I read some post about 32 bits mode running on 64 bits Windows 2003 Server and "Enable32bitAppOnWin64 true" trick. But the result of this is a "Service Unavailable" in a lot of environments. There are not documentation to this error in MSDN or Microsoft Forums. Could you confirm this situtation?

The main reason I chose this is to get the project out fast. I don't have time to mess around with flow layouts when I have a couple of months to churn the application out. I can get a page out really quick using absolute positioning. I've designed the screen to a standard 800 pixels wide so it looks decent on those that are using 600x800 resolution.

I've come across this advice you give above time and time again--but I don't agree at all when you are doing internal data entry sites. I structure my web apps to be similar to a windows app and the perform extremely well plus I can get them out the door in no time at all.

I'm using vista 64bit machine, i tried to solve the problem the way which you mentioned above...but whenever i'll give the code

borderstyle=2 && Fixed Dialog i need

i am facing the problem, that title bar of the form showing the background screen image.

I'm using with Visual Foxpro 7.0, will it work with VFP 9.0??

Thanks,
Siva

My problem is almost certainly the way we use the repeater templates and "mismatch" the DIV and Table tags around the Item Template to simulate a scrolling Browse window. This is a control I REALLY like the look and feel of. It is VERY useful.

I understand your comments, and appreciate the advantage of "living" in the code editor. However, I'm not experienced enough in HTML to do that (yet) - and it seems counter intuitive to use a product called Visual (anything) to develop Web Code as a text editor :-( Maybe I'm missing something? (Rhetorical question for Microsoft).

I'm never sure if VS2005 is "Quirky" or I just dont know enough :-( yet.

Something that drives me NUTS and wastes hours is that VS2005 goes off "helping" by adding closing tags, because it doesnt like the way I have the WW Repeater formatted with templates....

It does this every time I switch to design - announcing that it cant switch because of the tags it created not having starting tags .... Big Wow there!

All I had to do to get classic ASP running under Vista and IIS 7 was installing the ASP component together with the default IIS settings.

I installed VMware Server on Vista. Added W2K as a virtual OS inside VMware. Shared the folder in question from Vista. Set the folder as the base for the web site in my virtual W2K. Browsed it from Vista, and did all the editing in Vista as well.

Quite an awkward way of doing things, but considering the fact that I've been trying approximately 3-4 hours/day for a week to get Classic ASP to work under Vista, and this ad hoc solution took... well, an hour perhaps - including installation and configuration of W2K - I must say that I really can't justify the use of IIS7...

Anyway. Just thought that some frustrated person might find this solution useful, and that it therefore might be reason to share it... :)

Your general description seems to be good, or at least it seems to work for most people. Unfortunately not for me, though. I've enabled ASP (since classic ASP is what I want to be able to run - got a helluva lot of development going on using that, unfortunately, or something), but the server just continues to provide me weird error messages, when it isn't trying to force me to download the file. I've even enabled the option "allow unspecified CGI's and ISAPI's to run", but, alas, to no useful result.

<rant>
As far as I'm concerned IIS7 sucks. Big time.

It is easier for me to install VMware, a second operating system, and going through all that con figuration, than it is to make IIS7 work the way I want. Brilliant, huh? Not really.
</rant>

Well. Thank you anyway. Obviously your text helps a lot of people, and that is great, too bad I'm not one of them...

Rick, I have read an article about run-time compilation in .net, I guess few years ago.
Seems this topic is of your interest.

i have created web application & if i run it from D:\Test it will open a page called default.aspx. then i opened my IIS & created Virtual Directory calld Test, then i clicked browse for default.aspx & then i got

HTTP Error 404.3 - Not Found
Description: The page you are requesting cannot be served because of the Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web server. The page you requested has a file name extension that is not recognized, and is not allowed.

Error Code: 0x80070032

Notification: ExecuteRequestHandler

Module: StaticFileModule

Requested URL: http://localhost:80/Upload/Upload/Upload.aspx

Physical Path: E:\Work_Jayanth\Upload\Upload\Upload.aspx

Logon User: Anonymous

Logon Method: Anonymous

Handler: StaticFile

Most likely causes:

It is possible that a handler mapping is missing. By default, the static file handler processes all content.
The feature you are trying to use may not be installed.
The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)
What you can try:

In system.webServer/handlers:
Ensure that the expected handler for the current page is mapped.
Pay careful attention to preconditions (e.g. runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
Pay careful attention to typographical errors in the expected handler line.
Please verify that the feature you are trying to use is installed.
Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.
Open a command prompt and change directory to %windir%\system32\inetsrv.
To set a MIME type, use the following syntax: appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']
The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
For example, to add a MIME map for a file which has the extension ".xyz", type the following at the command prompt, and then press Enter:
appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']
Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them.
Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
More Information... This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files.

--------------------------------------------------------------------------------
Server Version Information: Internet Information Services 7.0.

Please disregard my previous posting as I figured out the answer myself.

I am trying to add script maps for Cold Fusion Pages and Cold Fusion Components. However, after I enter the information in the Add Script Map dialog box and click the OK button, another dialog box appears that says, "Would you like to enable this ISAPI extension? If yes, we will add your extensions as an Allowed entry in the ISAPI and CGI Restrictions list. If the extensions already exist we will allow it." No matter what I do from here, I am not able to save the script map. Please tell me what I should do to get these values accepted into the Handler Mappings.

Thank you,

The default BorderStyle in our system is resizable(3) and in numeral occasion we use fix border (about two-third ). The following sample code go through each form (SCX), remove BorderStyle statement from properties of 'form' object and reinsert it into last line of form init procedure.

By the way right click the program and "Run As Administrator" which is different from someone is administraor also give me the proper border display, but I can't expect every users to do that.

I sure hope VISTA SP1 will fix this problem.

-----------Sample code
nForms = ADIR( aForms, '*.scx' )
STORE 0 TO i, j
SET DELETED ON
SELECT 0

FOR i = 1 TO nForms
USE ( aForms[i,1] )
* assume all single for no formset
LOCATE FOR LOWER(TRIM(baseclass)) = 'form'
IF FOUND() AND 'BorderStyle' $ properties
SCATTER FIELDS uniqueid, properties, methods MEMO MEMVAR
m.dbfname = DBF()
= processMethod()
= updateForm()
ENDIF
ENDFOR

CLOSE DATABASES ALL

CLOSE DATABASES ALL

PROCEDURE processMethod()
* m.properties
* m.methods

LOCAL s1, s2, s3, n1, n2, nborder

nborder = LEN( 'BorderStyle = 2 ' )

s1 = LEFT( m.properties, ATC('BorderStyle', m.properties)-1 )
s3 = SUBSTRC( m.properties, LEN( s1 ) + 1 )
s2 = SUBSTRC( s3, nborder + 1 )
s3 = LEFTC( s3, nborder )
m.properties = s1 + s2

n1 = ATC( 'Procedure init', m.methods )
IF n1 = 0
m.methods = m.methods ;
+ 'PROCEDURE init' + CHR(13)+CHR(10) ;
+ s3 ;
+ 'ENDPROC'
ELSE
s1 = LEFTC( m.methods, n1 - 1 )
s2 = SUBSTRC( m.methods, n1 )
n2 = ATC( 'ENDPROC', s2 )
** check if there is .BorderStyle already in code, but we can't be sure if it is comment or active code
IF ATC( 'BorderStyle', LEFT( s2, n2) )=0
m.methods = STUFF( m.methods, n1 + n2 - 1, 0, 'thisform.' + s3 )
ENDIF
ENDIF
RETURN
ENDPROC

So what's the best place to install files that might get changed to?

No question, in a Network-environment the data goes on to the server.

But how about files like INI-Files, Helpfiles (that every now and then get updatet via online-Update), .... files that are not data but get modified eventually or every now and then without being a new "Setup"?

I have seen the hidden C:\ProgramData. A folder underneath that one could be an option or should we take the common Documents - folder as bases.

Sure, I'll make this a choosable option in my Setup, but what to take as default?

Regards from Berlin

Frank

This doesnt work on Vista. Can you tell me what has changed please.

My company is more concerned with basic compatibility and usability by our clients as they purchase Vista Computers. However, company management and I as well do not like the fact that the client will loose the Aero experience for the entire desktop and all apps running if they use either of these options.

Question: Is there a way to have our FoxPro 8 apps to run in the Vista Basic Theme or with the “Disable desktop composition.” and it only apply to our FoxPro app that is running and not the rest of the Windows Desktop and other apps that are running?

If all of you and the FoxPro community every figure out how to fix all the issue then we will re-evaluate the use of the Aero.

Thanks in advance for you help.

? FullPath( "c:\test\pra\ac1\..\adef1.dat")

To

C:\TEST\PRA\ADEF1.DAT

I assume you say the solution/workaround for this on Calvin's blog. It appears it will be fixed in VFP9 SP2. Of course, that doesn't help for VFP7 apps. !!!

http://blogs.msdn.com/calvin_hsia/archive/2007/05/01/windows-vista-aero-borderstyle-paint-problem-as-non-administrator.aspx

Here is what you need to do:
- Navigate to Handler Mapping feature of your virtual directory, and click on Add Script Map…
- Put “wc.dll” into “Request Path” field
- Put a physical path to wc.dll into “Executable” field
- Click OK
- Enjoy!

HTTP Error 500.0 - Internal Server Error

Description: The page cannot be displayed because an internal server error has occurred.

Error Code: 0x80070005

Notification: BeginRequest

Module: IIS Web Core

Requested URL: http://localhost:80/HandMadeCards

Physical Path: C:\Users\Iain\Documents\intraspin.com\Projects\Hand Made Cards

Logon User: Not yet determined

Logon Method: Not yet determined