|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
If your programs do run 正確に the first time, every time, you can skip this part of the 調書をとる／予約する. In fact, you should 令状 a 調書をとる／予約する and tell us how to do it. For the 残り／休憩（する） of you, we'll take a look at the 肉親，親類d of errors that occur in programs, give you some ideas on how to root them out, and show how VFP can 援助（する） your 成果／努力s.
Frequently Asked 力／強力にする 道具 Questions
現実に, some of these are frequently asked questions and others are "we 推定する／予想する these to be frequently asked" questions about things. There's a mix here of stuff we're tired of answering already (we hope putting it here will 削減（する） 負かす／撃墜する on the number of times we're asked) and things we think will be like that.
If you don't see your question here, check out "It's a Feature, Not a Bug"洋鉱石 of this 肉親，親類d of stuff is there. Some other items that might be on your "how do I" 名簿（に載せる）／表（にあげる） may be covered in the other 一時期／支部s in Section 2 of this 調書をとる／予約する. And if you still don't see your question, try one of the public support 会議s for VFP. (See the 虫垂 for a 名簿（に載せる）／表（にあげる） of places where 肉親，親類d folks answer questions and 雑談（する） about FoxPro.)
A Source is a Source, Of Course, Of Course
Wait! Don't flip that page! Source code 統合，差別撤廃 in Visual FoxPro is not just for team 開発! If you're a 単独の developer, or work in a group where each of you has your own 事業／計画（する）, source code 支配（する）／統制する is for you, too.
The 新規加入s that （機の）カム in Visual Studio 6 申し込む／申し出d greater 可能性s for tight 統合，差別撤廃 of Visual FoxPro 事業／計画（する）s with the other 道具s 供給（する）d in the Visual Studio 一括. Now that Visual FoxPro 7 is no longer in Visual Studio, we see no need to panic; it still 作品 with the other 道具s, 特に Visual SourceSafe. However, the 統合，差別撤廃 with Visual SourceSafe started with Visual FoxPro
Section 3 含む／封じ込めるs a bunch of stuff that didn't fit in anywhere else in the 調書をとる／予約する. Most of it can be 見解（をとる）d as 名簿（に載せる）／表（にあげる）s of one sort or another. You'll find our 金物類／武器類 推薦s, our opinionated 名簿（に載せる）／表（にあげる） of useless 命令（する）s to 避ける, optimization tips, and a collection of weird items that make you think you've 設立する a bug.
金物類／武器類 and ソフトウェア 推薦s (from a group of 金物類／武器類 haters) We hate 金物類／武器類. Let's get that one fact out from the beginning. IRQs and memory 場所s, obscure settings and incompatibilities are the 禁止（する） of our 存在. We're FoxPro hackers, not wire weenies, and it saddens us that FoxPro 要求するs any 金物類／武器類 at all預 事実上の machine would be so much nicer to work on! However, this is the real world, and it's a fact.
In the years since we first wrote this section for the Hacker's Guide to Visual FoxPro 3, much has changed, and yet much remains the same. We've seen a number of flavors of Windows ship, from Windows 95 to the just-解放（する）d (as of this 令状ing) Windows XP.
"It's a Feature, Not a Bug"
It's not surprising that a language with as many different roots as FoxPro has a number of 半端物 行為s葉hings that make you say "hmmm." Some of them, of course, are bugs. But this section is 献身的な to those that really aren't bugs葉he ones for which there's a 合法的 explanation. You'll also find a number of these items in the 言及／関連 section. Often, you'll find a design icon next to them.
命令（する）s Never To Use
Our fellow developers amaze us. Never have a group of such clever people created so many amazing 使用／適用s. And how they do it is 平等に stupendous, using 命令（する）s or features of this remarkable language that we knew of only peripherally, or with 能力s we only 嫌疑者，容疑者／疑うd. However, there are a few 命令（する）s whose use should be relegated to 遺産／遺物 code. These 命令（する）s have been 取って代わるd by better, newer or safer 命令（する）s; never really had a 推論する／理由 to 存在する in the first place; or they just plain break the machine.
We divide our 名簿（に載せる）／表（にあげる） into two parts: 命令（する）s that should never, ever be used, and 命令（する）s that should only be used from the 命令（する） Window. Some 命令（する）s are just useless, and we have a few favorites that we recommend you 避ける altogether. But then, there are some 命令（する）s that do useful things but have too many 味方する 影響s to let us feel comfortable bringing them into a （弁護士の）依頼人's 使用／適用.
Faster Than a スピード違反 弾丸
速度(を上げる） is where it's at. No （弁護士の）依頼人 is going to 支払う／賃金 you to make his app run slower. Fox ソフトウェア's 初期の （人命などを）奪う，主張する to fame was that FoxBASE (and later, FoxBASE+ and FoxPro) ran faster than its competitors. Fox's 評判 for 速度(を上げる） was 井戸／弁護士席 deserved. However, the 速度(を上げる） 伸び（る） has never been (a)自動的な／(n)自動拳銃. You have to do things 権利 to make your code "run like the Fox."
The Rushmore optimization 科学（工学）技術 introduced in FoxPro 2.0 is based on 索引s. Rushmore 診察するs 索引 とじ込み／提出するs to 決定する which 記録，記録的な／記録するs 会合，会う the 条件s for a particular 命令（する）. So, ーするために make things 急速な／放蕩な, it's important to create the 権利 索引s and to 令状 code that takes advantage of those 索引s. The difference between the 雷-急速な／放蕩な code your （弁護士の）依頼人 uses to make 決定的な 戦略の 決定／判定勝ち（する）s and the plodding code his 競争 uses might 異なる by no more than an 操作者 or two, so listen up!
There are also some other tricks, not 関係のある to Rushmore, that can 速度(を上げる） up your 使用／適用s かなり. This section discusses both Rushmore and 非，不，無-Rushmore optimization techniques.
Section 4 is the meat of the Hacker's Guide. You'll find a 名簿（に載せる）／表（にあげる）ing for every 命令（する）, 機能（する）／行事, 所有物／資産／財産, event, method and system variable. We've grouped them 論理（学）上 so that you can find several 関係のある topics in one place.
We've sliced, we've diced, we've chopped Visual FoxPro into little pieces. But there's still more to say. A few features are so 冷静な／正味の, they 令状 their own 一時期／支部s. This section goes into 詳細（に述べる） on the ActiveX 科学（工学）技術s, the 反対する Browser and 構成要素 Gallery, Wizards and 建設業者s, and IntelliSense, all of which 供給する 適切な時期s for 延長するing your use of VFP.
Active Something
In the 初めの Hacker's Guide to Visual FoxPro 3.0, we 含むd a 一時期／支部 "OLE, OLE, Oxen 解放する／自由な!" that talked about the 勇敢に立ち向かう new world of OLE. Even at that time, OLE was not that new, but it was just catching on in the developer community. FoxPro 2.x 供給するd support only for OLE 1.0 in its 実施, and that was pretty weak. Visual FoxPro supported OLE 2.0 but, like many "point 無" 解放（する）s, there were a lot of 相いれない 製品s 解放（する）d under the 2.0 旗，新聞一面トップの大見出し／大々的に報道する.
We've made a somewhat 独断的な 決定／判定勝ち（する） to divide the ever-拡大するing 支配する of OLE, er, COM, into several pieces. "It was Automation, You Know" covers those 科学（工学）技術s 以前は known as OLE Automation, now 簡単に Automation, 同様に as the 勇敢に立ち向かう new world of Automation servers created with Visual FoxPro. In this section, we take on a few of the other 面s of the 科学（工学）技術, and look at the Registry, linking and embedding, and ActiveX 支配（する）／統制するs.
切り開く／タクシー／不正アクセスing the Class Browser and 構成要素 Gallery
Visual FoxPro's Class Browser and 構成要素 Gallery (or just "Browser" and "Gallery") are 価値のある 開発 道具s; most self-尊敬（する）・点ing VFP 切り開く／タクシー／不正アクセスs will want to know them 井戸／弁護士席.
Most of Visual FoxPro's ancillary 道具s, like Browser and Gallery, are 現実に written in Visual FoxPro. (Surprised?) Starting with VFP 6, the source code for all the VFP-coded 道具s is 含むd. This is 広大な／多数の／重要な news for VFP developers because the source for these 道具s 供給するs some 広大な／多数の／重要な (and occasionally not so 広大な／多数の／重要な) examples. If you search carefully, you may even find an astonishing feat of ソフトウェア prowess: a comment in the source code.
欠如（する） of comments aside, if you've ever wondered just how a particular wizard or service 作品, you can now easily and 合法的に 逆転する-engineer it.
建設業者s and Wizards (and 耐えるs, Oh My!)
Visual FoxPro comes with things called 建設業者s and wizards. Other Microsoft 製品s, like 接近 for example, are bundled with only wizards. The difference? Mostly parlance. 建設業者s and wizards are very 類似の. The difference depends on which part of the 開発 過程 you're working on.
IntelliSense and Sensibility
Visual FoxPro developers have long had VB-envy, at least with regard to one particular feature: IntelliSense. Type a 声明 such as "薄暗い SomeVariable As" in Visual Basic and a 名簿（に載せる）／表（にあげる） すぐに pops up of all of the types a variable can be defined as妖ata types 同様に as 反対するs. Type "SomeObject." and you're 現在のd with a 名簿（に載せる）／表（にあげる） of the 所有物／資産／財産s, events and methods for that 反対する. This feature is a 広大な／多数の／重要な 生産性 booster for several 推論する／理由s: You can quickly 選ぶ the item you want from the 名簿（に載せる）／表（にあげる）, it 避けるs （一定の）期間ing mistakes, and it 削減（する）s 負かす／撃墜する on trips to the Help とじ込み／提出する to 人物／姿／数字 out the syntax for a little-used 命令（する）.
VFP 7 cures our inferiority コンビナート／複合体 by 追加するing IntelliSense to our beloved 道具, and makes up for the long wait by 供給するing a better 見解／翻訳／版 of IntelliSense than Microsoft's other 製品s have (in fact, the VFP team has been showing their 冷静な／正味の 見解／翻訳／版 to the other 製品 teams). Once you start 高く評価する／（相場などが）上がるing how much more 生産力のある IntelliSense makes you, you'll wonder how you ever coded without it.
IntelliSense 供給するs VFP developers with several very useful 行為s: (a)自動的な／(n)自動拳銃 keyword 完成, 命令（する） and 機能（する）／行事 syntax tips, and 名簿（に載せる）／表（にあげる）s of members, values, and most recently used とじ込み／提出するs.
資源 とじ込み／提出する
In this section we 名簿（に載せる）／表（にあげる） many 資源s we think may be of 利益 to you. These 含む 調書をとる／予約するs 価値（がある） reading, either for their value as a 言及／関連 or as food for thought. に引き続いて that 名簿（に載せる）／表（にあげる） is a 名簿（に載せる）／表（にあげる） of FoxPro 2.x 調書をとる／予約するs to 援助（する） in your understanding of "遺産／遺物" code and techniques. 含むd at the end is a 名簿（に載せる）／表（にあげる） of other 資源s 価値（がある） checking into. Finally, there are a number of other good 調書をとる／予約する 名簿（に載せる）／表（にあげる）s out there.
What's in the Downloads?
With this 版 of the Hacker's Guide, we've 受託するd that the Internet is for real and 含むd より小数の items in the downloads than in previous 見解／翻訳／版s. Our thinking is that most of you don't want to download a トン of stuff you're never going to use ーするために get the one or two items you do want. Instead, in the "資源 とじ込み／提出する" section, we've given some idea of what's out there and where to get it. The actual download is left as an 演習 to the reader.