silahkan download update untuk Laporan Kenaikan pangkat berdasarkan kategori pilihan
klik DOWNLOAD UPDATE Laporan Kenaikan pangkat berdasarkan kategori pilihan (FEB 2008)
setelah di download double klik update_laporan.exe untuk melakukan update laporan tetapi sebelumnya ditutup dulu aplikasi SIMPEG nya
So what is is Forex trading you may ask? Forex is the exchange you can buy and sell currencies. For example, you might buy British pounds (by exchanging them to the dollars you had), then, after pounds / dollar ratio goes up, you sell pounds and buy dollars again. At the end of this operation you are going to have more dollars, then you had at the beginning.
The Forex market has much higher liquidity, then the stock market, as much more money is being exchanged. Forex is spread between banks all over the planet and as a result it means 24 hour trading.
Unlike stocks, Forex trades are performed with high leverage, usually it is 100. It means that by investing $1000 you can control $100,000, and increase potential profits accordingly. Some brokers provide also so called mini-Forex, where the size of minimum deposit equals $100. It makes possible for individuals to enter this market easily.
The name convention. In Forex, the name of a “symbol” is composed of two parts - one for first currency, and another for the second currency. For example, the symbol usdjpy stands for US dollars (usd) to Japanese yen (jpy).
As with stocks, you can apply tools of the technical analysis to Forex charts. Trader’s indexes can be optimized for Forex “symbols”, allowing you to find winning strategy.
Example Forex transaction
Assume you have a trading account of $25,000 and you are trading with a 1% margin requirement. The current quote for EUR/USD is 1.3225/28 and you place a market order to buy 1 lot of 100,000 Euros at 1.3228, expecting the euro to rise against the dollar. At the same time you place a stop-loss order at 1.3178 representing a maximum loss of 2% of your account equity if the trade goes against you, 50 pips below your order price, and a limit order at 1.3378, 150 pips above your order price. For this trade, you are risking 50 pips to gain 150 pips, giving you a risk/reward ratio of 1 part risk to 3 parts reward. This means that you only need to be right one third of the time to remain profitable.
The notional value of this trade is $132,280 (100,000 * 1.3228). Your required margin deposit is 1% of the total, which is equal to $1322.80 ($132,280 * 0.01).
As you expected, the Euro strengthens against the dollar and your limit order is reached at 1.3378. The position is closed. Your total profit for this trade is $1500, each pip being worth $10.
by Richard Goldie
There are many markets: markets for stocks, futures, options and currencies. These are probably the most accessible markets for everyday traders like you and I. People easily understand the basics of trading shares, so I will occasionally use examples from that market.
I began trading shares first and then I moved on to trading currencies; therefore, most of the examples I will be using in this book are derived from trading currencies.
If you do not know a lot about currency trading, allow me to introduce it to you. It is what I trade and I believe that it is one of the best markets to trade because of its efficiency. The transaction costs to execute a trade are minimal and most brokers provide you with the tools and data you need to make your trading decisions, they usually provide them for free. The market is open 24 hours a day which allows you to design your trading hours around your daily commitments. It is very volatile, which is great for those people who are looking for day-trading opportunities.
The foreign exchange market is the market in which currencies are bought and sold against one another. People may loosely refer to this market under different labels, including foreign exchange market, forex market, fx market or the currency market.
The foreign exchange market is the largest market in the world, with daily trading volumes in excess of $1.5 trillion US dollars. All transactions involving international trade and investment must go through this market because these transactions involve the exchange of currencies.
It is the most perfect market that exists because it has a large number of buyers and sellers all selling the same products. There is a free flow of information and there are little barriers to participate.
The currency exchange market is an over-the-counter (OTC) market which means that there is not one specific location where buyers and sellers can actually meet to exchange currencies. Instead, transactions are conducted by phone, fax, e-mail or through the websites of brokers who specialize in currency trading.
The major dealing centres at the time of writing are: London , with about 30% of the market, New York , with 20%, Tokyo , with 12%, Zurich , Frankfurt, Hong Kong and Singapore , with about 7% each, followed by Paris and Sydney with 3% each. Because of the fact that these centres are all over the world, foreign exchange traders can execute transactions 24 hours a day. The market only closes on the weekends.
THE MAIN ‘PLAYERS’ IN THE FOREX MARKET
The five broad categories of participants are: consumers, businesses, investors, speculators, commercial banks, investment banks and central banks.
Consumers, including visitors of countries, tourists and immigrants, do need to exchange currencies when they travel so that they can buy local goods and services. These participants do not have the power to set prices. They just buy and sell according to the prevailing exchange rate. They make up a significant proportion of the volume being traded in the market.
Businesses that import and export goods and services need to exchange currencies to receive or make payments for goods they may have bought or services they may have rendered.
Investors and speculators require currencies to buy and sell investment instruments such as shares, bonds, bank deposits or real estate.
Large commercial and investment banks are the ‘price makers’. They are the ones who buy and sell currencies at the bid-and-offer exchange rates that they declare through their foreign exchange dealers.
Commercial banks deal with customers on one hand, and with the Interbank or other banks, on the other hand. They profit by utilizing the bid-and-offer spread. The bid price is the exchange rate that the buyer is willing to buy and the offer price is the exchange rate at which the seller is willing to sell. The difference is called the bid-offer spread. They also make profits from speculating about whether the exchange rate will rise or fall.
Central banks participate in the foreign exchange market in their effective duty as banks for their particular government. They trade currencies not for the intention of making profits but rather to facilitate government monetary policies and to help smoothen out the fluctuation of the value of their economy’s currency.
by Marquez Comelab
please download all files to get the new releases of Credia Application
1. CrediaInstaller28Okt2007.rar.1
2. CrediaInstaller28Okt2007.rar.2
3. CrediaInstaller28Okt2007.rar.3
4. Create_CrediaInstaller28Okt2007.exe
thanks a lot
silahkan download update untuk beberapa report dan data data yang perlu di maintenance lebih lanjut
What’s a DSN ?
According to Microsoft documentation, it means “The name that applications use to request a connection to an ODBC data source.” In other words, it is a symbolic name that represents the ODBC connection. It hides the connection details like database name, directory, database driver, UserID, password, etc. So when making a connection to the ODBC, you don’t have to remember the database name, where it resides, etc.
So, what’s a file DSN ?
Before we discuss this, let me the list the various types of DSNs.
· System DSN: This is the DSN used through out the system, no matter which user logs in. Meaning, all users on the system can see this DSN and use it (as long as they know the user ID and password). The connection parms are stored in the registry.
· User DSN: This is a DSN created for a specific user. Only the user who created the DSN can see this and use it. Like System DSN, the information is stored in the registry.
In both these two cases, DSN details are stored in the system registry.
With that, let me explain what a file DSN is. Instead of storing the DSN details in registry, you store it in a file - simple ?! Yes, it is. The file is a simple text file, with a .DSN extension.
Although it sounds simple, you need to know the parameters that make up a DSN. But again, it is not all that difficult, as you can look this up in any ODBC reference, or online help that comes with Visual Basic or Access.
Creating file DSNs and reusing them
Shown below is a generic file DSN for an MS Access database.
————- file.dsn ——-
[ODBC]
DRIVER=Microsoft Access Driver (*.mdb)
ReadOnly=0
UserCommitSync=Yes
Threads=3
SafeTransactions=0
PageTimeout=5
MaxScanRows=8
MaxBufferSize=512
ImplicitCommitSync=Yes
FIL=MS Access
DriverId=25
I call the file file.dsn, you may rename it appropriately.
Creating this file is half work done. The next step is creating a connection. When using a system DSN, you create a connection by simply using the system DSN name, something like
Conn.Open “MyDSN”
While using the file DSN shown above, you need a few more parameters I purposely left out so that you could reuse the file DSN. The final connection string will look like
“filedsn=c:\webdir\file.dsn;DBQ=c:\database\mydb.mdb;UID=admin;PWD=admin;”
c:\webdir is the directory where file DSN resides. This requires a physical path to the file. On an ISP, you could use Server.mapPath method to determine this directory. Something like
Server.MapPath(”/mysite/file.dsn”)
the same holds for DBQ parameter. UID and PWD are optional.
In summary, to create a reusable file DSN
Create a text file with DSN parameters. This file has a .dsn extension
Create the connection string, with the filedsn and DBQ parameters. You can determine physical paths using Server.MapPath method
Use the DSN for as many databases you want, by changing just the DBQ, UID and PWD parameters
Note that databases other than MS Access require different values for parameters and also some additional parameters.
ODBC (Open Data Base Connectivity) is a standard database access method that makes it possible to access any data from
any application, regardless of which database management system (DBMS) is handling the data. ODBC inserts a middle
layer, called a database driver, between an application and the DBMS. The purpose of this layer is to translate the
application’s data queries into commands that the DBMS understands. For this to work, the application must be capable of
issuing ODBC commands, and the DBMS must be capable of responding to them.
ODBC Connection Setup
1. Check if the Sybase ODBC driver is installed on the PC.
2. Check if a sql.ini file exists on the PC with a reference to the Sybase server housing the Data Warehouse.
3. Create a data set name (DSN) referring to the Data Warehouse server.
4. Connect to Data Warehouse server in Microsoft Access, and link desired Data Warehouse tables into MS Access.
5. Create a query.
Step 1: Check if the Sybase ODBC driver is installed on your PC. Click on the Start button, point to Settings, and then click
on Control Panel. Double-click on Administrative Tools, and then double-click on ODBC Data Source Administrator. Click
on the Drivers tab. Scroll down the list and look for “Sybase System 11, as indicated in Figure 1 below.
Figure 1
If you do not see the Sybase Driver, you will need to download the driver from
http://www.columbia.edu/cu/sis/Downloads/downloads.html, which will install SYSYBNT.DLL, the Sybase ODBC driver
on your PC.
Step 2: Check if a “sql.ini” file exists on your PC with a reference to the Data Warehouse Server. The sql.ini is usually
found in the c:\sql\ini folder. (If you downloaded the SDR package, a sql.ini file should have been created.) Once you have
This line indicates that the Sybase
ODBC driver is installed.
opened the sql.ini file, you will see a number of entries referring to various Columbia servers. The entry for the Data
Warehouse server should look like this:
[drep_pdb]
query=NLWNSCK, drep-pdb.ais.columbia.edu,4100
win3_query=WNLWNSCK, dwr-pdb.ais.columbia.edu,4100
If none of the entries look like the one specified above, then cut and paste it into your sql.ini file.
Step 3: Create a Data Source Name (DSN) referring to the Data Warehouse server. (DSN provides connectivity to a
database through an ODBC driver.) The DSN contains the database name, directory, database driver, User ID, password, and
other information. Once you create a DSN for a particular database, you can use the DSN in an application to call
information from the database.
1. Click on the Start button, point to Control Panel, double-click Administrative Tools, and then double-click Data
Sources(ODBC).
2. Click the System DSN or the User DSN tab, and then click Add.
3. Choose the Sybase System 11 driver and then click Finish.
4. Enter the information on the General tab as shown in Figure 2 below.
5. If you would like to use this DSN to access multiple databases (such as DSS and SIS), click on the Connection tab,
and in the Database List box, enter the database names, separated by commas (for example: DSS, SIS).
6. Click OK and then click OK on the next window.
Figure 2
Step 4: Connect to the Data Warehouse server in MS Access, and link desired Data Warehouse tables into Access.
1. Open MS Access, and either create a new database file or open an existing database file. Go to the Database
window for the open file.
2. On the File menu, point to Get External Data, and then click Link Tables.
3. In the Link dialog box, in the Files of type box, select ODBC Databases().
4. Click either the File Data Source or Machine Data Source tab, and then double-click the ODBC data set name for
the Data Warehouse.
5. Enter your Data Warehouse logon ID and password and then click OK. MS Access will connect to the Data
Warehouse and display a list of the tables you can link to.
6. Click each table that you want to link to, and then click OK. If you’re linking a table and it doesn’t have an index
that uniquely identifies each record, then MS Access displays a list of the fields in the linked table. Click a field or
a combination of fields that will uniquely identify each record, and then click OK.
7. Since MS Access allows you by default to upate data in a table, you should protect Data Warehouse linked tables
so that you or another user will not inadvertently attempt to update the tables. To do this, go to the Tools menu,
point to Security, and click on the User and Group Permissions. For each one of your linked tables, unclick the
check boxes that allow users to update, delete or insert data.
Step 5: Create a query from the tables selected in Step 4.
1. Click on Queries.
2. Double-lick on Create Query in Design View.
3. Select the tables you would like to use in your query and click Add.
4. Once the tables have been added to the query you can begin your table joins. (See Data Warehouse
Database Reference Manual https://dwr.ais.columbia.edu/info/Data%20Warehouse%20Manual.pdf for
complete descriptions of recommended table joins.)
5. Drag and drop the columns from each table into your work area. (Another method would be to click on the
box beside the word “Field”, click on the scroll-down arrow and select the columns you need from each
table.)
6. Select the columns the output should be sorted by.
7. Select columns to be or not to be displayed in the output.
8. Enter the criteria for the query. For example, for Fiscal_Year 2004 enter 2004 in the Fiscal Year column.
9. Click on the Red Exclamation Sign to run the query.
10. To return to the query section, click on view on the toolbar, click Design view and it will return you to your
query page.
Once you have completed the above steps you should have successfully connected to the Data Warehouse server and residing
tables.
View products that this article applies to.
| Article ID | : | 830761 |
| Last Review | : | May 18, 2007 |
| Revision | : | 2.9 |
Prepare to deploy your Visual Basic 6.0 application
Plan ahead and budget time to package and to test your application
Prepare the development computer and the packaging computer
Identify and minimize application dependencies
Troubleshoot deployment issues of Visual Basic 6.0 applications
Tools for troubleshooting deployment issues
Common deployment issues of Visual Basic applications
Common deployment issues of database applications
Deploy your Visual Basic 6.0 application by using alternative installer technologies
Redistribute minimum dependencies
Build a Setup package by using the Package and Deployment Wizard
This article discusses how to prepare to deploy a Microsoft Visual Basic 6.0 application.
To prepare a Visual Basic 6.0 application for deployment, make sure that you do the following:
| • |
Plan ahead and budget time to package and to test the application. |
| • |
Package the application on a “clean” computer. |
| • |
Use the same software configuration on both the development computer and the packaging computer. |
| • |
Identify and minimize application dependencies. |
| • |
Prepare the Package and Deployment Wizard Redist folder. |
To troubleshoot a deployed Visual Basic 6.0 application, use the following methods:
| • |
Use the tools for troubleshooting deployment issues. |
| • |
Review common deployment issues. |
To troubleshoot a deployed Visual Basic 6.0 application that was installed by using an alternative installer technology, use the following methods:
| • |
Redistribute minimum dependencies. |
| • |
Build a Setup package by using the Package and Deployment Wizard. |
Before you deploy a Visual Basic 6.0 application, you must plan how you want to build and to deploy the package that installs the application. You must also decide what files you want to include in the package. Additionally, you must test the package before you deploy it to make sure that the installed application works as expected. This article discusses issues that you must consider and tools that you can use to deploy your application.
When you are preparing to deploy a Visual Basic 6.0 application, consider how much time you will require to package and to test the application. Include time to prepare the computers that you will use, time to identify and to minimize application dependencies, and time to prepare the Redist folder that contains the correct versions of files that you want to redistribute with the application.
Many developers spend lots of time and effort to develop an application, and then they spend little time or no time to package and to test the application on other computers. This is a common mistake. It is best to budget time into your development schedule for packaging and for testing your application. Consider which operating system versions and which configurations you will support for your application, and budget time for testing the application on those configurations.
The Visual Basic 6.0 Package and Deployment Wizard was designed to deploy applications to Microsoft Windows 95, Windows 98, and Microsoft Windows NT 4.0 or later. However, for obsolete operating systems, such as Windows 95, Microsoft provides support for deploying Visual Basic 6.0 applications on a “best effort” basis after the problem is identified as being specific to the operating system.
For information about the life cycle of a specific version of Internet and MSN, visit the following Microsoft Web site:
http://support.microsoft.com/gp/lifeselectintmsn (http://support.microsoft.com/gp/lifeselectintmsn)
Note Microsoft does not provide support for deploying or for running Visual Basic 6.0 applications on Windows NT 4.0 Terminal Server.
For more information about how to run Visual Basic 6.0 applications on Windows NT 4.0 Terminal Server, click the following article number to view the article in the Microsoft Knowledge Base:
196201 (http://support.microsoft.com/kb/196201/) Visual Basic is not supported on Terminal Server 4.0
When you are preparing to develop and to package a Visual Basic 6.0 application, consider the following best practices:
| • | Package on a “clean” computer. A “clean” computer is a computer that has only the required software installed to develop and to package a Visual Basic application. At a minimum, that software includes only the operating system and Visual Studio 6.0.
If your application requires other components, you must also install them. However, it is a good idea to avoid installing anything that is not required, such as beta software, or anything that might change the redistributable files that your application package requires. |
||||||||
| • | Install the latest operating system and the latest Visual Studio 6.0 service pack. Make sure that you have installed the latest service packs and that you have applied the latest updates for the operating system on both the development computer and the packaging computer. To apply the latest updates for your computer, visit the following Microsoft Windows Update Web site:
http://windowsupdate.microsoft.com (http://windowsupdate.microsoft.com) Additionally, make sure that you have installed the latest Visual Studio 6.0 service pack on both the development computer and the packaging computer. To obtain the latest Visual Studio 6.0 service pack, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn2.microsoft.com/en-us/vstudio/aa718359.aspx (http://msdn2.microsoft.com/en-us/vstudio/aa718359.aspx) |
||||||||
| • | Make sure that the development computer and the packaging computer have the same software. If you are packaging the application on a computer other than the development computer, make sure that both computers have the same software configuration. For example, make sure that both computers:
Additionally, if you are packaging the application on a computer other than the development computer, make sure that the compiled versions of your binaries work correctly on the packaging computer. If you receive an error message when you run your application on the packaging computer, the error message may indicate that one of the application’s dependencies is missing or has a versioning problem. |
Missing or mismatched versions of application dependencies are the most common cause of problems that developers experience when they distribute Visual Basic 6.0 applications. Therefore, it is extremely important that you identify exactly what dependencies your application requires, and their versions. This way, you can make sure that you are redistributing the correct dependencies with your application.
Generally, the Package and Deployment Wizard does a good job of redistributing the correct dependencies for your application. However, to minimize problems, minimize the dependencies that your application requires.
The main dependencies in a Visual Basic 6.0 application are component references and COM library references. Component references include ActiveX controls or designers that are located in an external .ocx file or in an external .dll file. When you select an ActiveX control in the Components dialog box, Visual Basic puts an icon for the control in your control toolbox and then adds a reference to the external library in the Visual Basic project.
If a component requires a supporting DLL, Visual Basic automatically adds the DLL as a library reference in the References dialog box. A COM library reference is a reference to a type library (DLL, TLB, OLB) that has been selected in the References dialog box.
When the Package and Deployment Wizard determines the files to deploy with your application, the Package and Deployment Wizard reviews the project file to determine which components and which COM library references the project uses. The Package and Deployment Wizard then searches for any dependency files (.dep) that are associated with these components to determine if any supporting files must be redistributed with the application.
Verify that the project does not reference any components or libraries that are not required so that the Package and Deployment Wizard does not try to redistribute files that the application does not require.
To identify and to minimize references to components in your project, follow these steps:
| 1. | Open your project in Visual Basic 6.0. |
| 2. | On the Project menu, click Components. |
| 3. | Click to select the Selected Items Only check box to view only the components that your project currently references. |
| 4. | Click to clear the check box next to any component that your project does not use.
Note If you do not know whether your project uses a component, click to clear the check box next to that component. If you receive an error message that is similar to the following, your application uses that component: Can’t remove control or reference; in use Typically, the component is a control that is used on a form. |
| 5. | For the remaining components that are selected, make a note of the version and the location of the library that your application is using. |
| 6. | To close the Components dialog box, click OK. |
To identify and to minimize references to COM libraries in your project, follow these steps:
| 1. | Open your project in Visual Basic 6.0. | ||||||
| 2. | On the Project menu, click References. | ||||||
| 3. | Notice the reference libraries that are selected. Every Visual Basic 6.0 application requires the following references. You cannot remove these references.
Other reference libraries that are selected may not be required for your application. |
||||||
| 4. | To remove a reference to a reference library that your application does not use, click to clear the check box next to the reference library name.
Note If you do not know whether your application uses a reference library, click to clear the check box to that reference library. If you receive an error message such as the following, your application uses that reference library: Can’t remove control or reference; in use Restore these references before you go to step 5. |
||||||
| 5. | For the remaining references that are selected, make a note of the version and the location of the reference library. | ||||||
| 6. | To close the References dialog box, click OK. |
The Redist folder is located on the packaging computer. By default, the Redist folder is located in the following folder:
C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard
After the Package and Deployment Wizard determines the application’s dependencies, the Package and Deployment Wizard tries to locate the files that it has determined must be included with the Setup package. The first location that the Package and Deployment Wizard scans is the Redist folder.
If the Package and Deployment Wizard does not locate the required files in the Redist folder, it tries to locate the files in other folders, such as the System32 folder. This behavior may cause problems because your operating system may contain versions of system files that are not compatible with earlier operating systems. Therefore, make sure that the Redist folder contains the correct versions of any files that the Package and Deployment Wizard copies from your system.
If you have installed Visual Basic 6.0 Service Pack 4 or later, the Redist folder already contains most of the files that the Package and Deployment Wizard requires for the package. However, if you have specific versions of files that you want to redistribute with the application, make sure that you copy them manually to the Redist folder.
Additionally, if you use a packaging script that you have saved from an earlier application packaging project, the Package and Deployment Wizard collects the files from the location that appears in the earlier packaging script. The Package and Deployment Wizard will not collect the dependencies from the Redist folder unless it collected them from the Redist folder earlier.
Many tools and resources exist to help you troubleshoot the deployment of your Visual Basic 6.0 application. The following tools and link provide information that you can use to troubleshoot common issues that may occur when you deploy your application.
The following tools monitor registry access, monitor file access, determine file dependencies, and determine the versions of loaded modules.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Regmon (Regmon.exe) monitors registry access on a real-time basis. You can use Regmon to determine which applications are accessing the Windows registry. For more information about Regmon, visit the following Sysinternals Freeware Web site:
http://www.microsoft.com/technet/sysinternals/default.mspx (http://www.microsoft.com/technet/sysinternals/default.mspx)
To use Regmon, follow these steps:
| 1. | Install Regmon. To obtain Regmon, visit the following Sysinternals Freeware Web site:
http://www.microsoft.com/technet/sysinternals/utilities/regmon.mspx (http://www.microsoft.com/technet/sysinternals/utilities/regmon.mspx) |
| 2. | Start Regmon. Notice that Regmon immediately starts to log all registry activity. |
| 3. | On the File menu, click to remove the check mark next to Capture Events to stop logging. |
| 4. | Prepare your application for monitoring. When you are ready to monitor your application, go to step 5. |
| 5. | On the File menu in Regmon, click to select Capture Events. |
| 6. | Reproduce the problem that you are trying to solve. |
| 7. | Switch to Regmon, and then click to remove the check mark next to Capture Events to stop logging. |
| 8. | On the File menu, click Save. Save the log file as a .log file so that you can analyze the output.
Note You may want to import the .log file into Microsoft Excel so that you can filter the data more easily. |
For more information about Regmon, see the Regmon online Help file.
Filemon (Filemon.exe) monitors file access on a real-time basis. You can use Filemon to determine which applications are accessing files on the system. For more information about Filemon, visit the following Sysinternals Freeware Web site:
http://www.microsoft.com/technet/sysinternals/default.mspx (http://www.microsoft.com/technet/sysinternals/default.mspx)
To use Filemon, follow these steps:
| 1. | Install Filemon. To obtain Filemon, visit the following Sysinternals Freeware Web site:
http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx (http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx) |
| 2. | Start Filemon. Notice that Filemon immediately starts to log all file activity. |
| 3. | On the File menu, click to remove the check mark next to Capture Events to stop logging. |
| 4. | Prepare your application for monitoring. When you are ready to monitor your application, go to step 5. |
| 5. | On the File menu in Filemon, click to select Capture Events. |
| 6. | Reproduce the problem that you are trying to solve. |
| 7. | Switch to Filemon, and then click to remove the check mark next to Capture Events to stop logging. |
| 8. | On the File menu, click Save. Save the log file as a .log file so that you can analyze the output.
Note You may want to import the .log file into Microsoft Excel so that you can filter the data more easily. |
For more information about Filemon, see the Filemon online Help file.
Dependency Walker (Depends.exe) is used to determine the explicit dependencies that a file has. A dependency is a secondary file that a file requires to load or to run correctly. For example, a Microsoft Visual Basic application depends on the Microsoft Visual Basic run-time files.
Dependency Walker also includes a profiling feature that you can use to monitor the way that your application loads and the way that your application runs. This feature is useful for troubleshooting a Visual Basic application that has problems during startup. For more information about Dependency Walker, visit the following Dependency Walker Web site:
http://www.dependencywalker.com (http://www.dependencywalker.com)
To use Dependency Walker to profile your application, follow these steps:
| 1. | Install Dependency Walker. To obtain Dependency Walker, visit the following Dependency Walker Web site:
http://www.dependencywalker.com (http://www.dependencywalker.com) |
| 2. | Start Dependency Walker. |
| 3. | On the File menu, click Open. |
| 4. | In the Open dialog box, click the application’s .exe file, and then click Open. |
| 5. | On the Profile menu, click Start Profiling. |
| 6. | In the Profile module dialog box, configure the options that you want, and then click OK. |
You can view the log window while your application is loading to see which modules load successfully.
For more information about Dependency Walker, see the Dependency Walker online Help file.
ListDLLs outputs the names and the versions of all modules that are loaded in a specific process. You can use ListDLLs when a deployed application works on some computers but not on others. You can also use it to compare the versions of modules that are loaded. This information is helpful for determining if any mismatches exist between the loaded modules and your application’s dependencies.
To use ListDLLs, follow these steps:
| 1. | Install ListDLLs. To obtain ListDLLs, visit the following Sysinternals Freeware Web site:
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ListDlls.mspx (http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ListDlls.mspx) Note ListDLLs is a console application. Therefore, you may want to copy the ListDLLs.exe file to a folder that is easily accessible on the computer, such as C:\. |
| 2. | Start your application. |
| 3. | At the command prompt, type the following command, and then press ENTER:
Listdlls MyApplication.exe > C:\MyApplicationOutput.txt |
The output file will contain the names and the versions of all modules that were loaded in process to your application.
For more information about tools that you can use to troubleshoot deployed Visual Basic 6.0 applications, click the following article numbers to view the articles in the Microsoft Knowledge Base:
198038 (http://support.microsoft.com/kb/198038/) Useful tools for Package and Deployment issues
For more information about common issues with deploying Visual Basic 6.0 applications, click the following article numbers to view the articles in the Microsoft Knowledge Base:
831491 (http://support.microsoft.com/kb/831491/) You receive multiple “System files are out of date” error messages when you install a Visual Basic 6.0 application
193270 (http://support.microsoft.com/kb/193270/) Troubleshooting VB application installation issues
330314 (http://support.microsoft.com/kb/330314/) Your computer does not restart after you install a Microsoft Visual Basic 6.0 application that includes a Msvcrt.dll file
216231 (http://support.microsoft.com/kb/216231/) Application Setup errors while displaying “copying files, please stand by”
200271 (http://support.microsoft.com/kb/200271/) How to diagnose and resolve some automation errors
254166 (http://support.microsoft.com/kb/254166/) Distribution of Microsoft Scripting Runtime Library fails
216158 (http://support.microsoft.com/kb/216158/) Multiple “please insert disk” messages when installing VB6 application
197580 (http://support.microsoft.com/kb/197580/) Distribution issues with Riched32.dll
For more information about common issues with deploying Visual Basic 6.0 database applications, click the following article numbers to view the articles in the Microsoft Knowledge Base:
213846 (http://support.microsoft.com/kb/213846/) Deploy database applications with the Package and Deployment Wizard (PDW)
299457 (http://support.microsoft.com/kb/299457/) Error “can’t find installable ISAM” when you connect to Access database with intrinsic DataControl
217754 (http://support.microsoft.com/kb/217754/) How to control which MDAC version the Package and Deployment Wizard (PDW) distributes
299645 (http://support.microsoft.com/kb/299645/) Error “unable to register Msado15.tlb” if you use a PDW package to install a VB application
Frequently, developers deploy Visual Basic 6.0 application packages by using alternative installer technologies, such as Microsoft Windows Installer, instead of by using the Package and Deployment Wizard. However, if you use alternative installer technologies, unexpected problems may occur during deployment.
Note Microsoft only supports the deployment of a Visual Basic 6.0 application if you deploy the application by using the Package and Deployment Wizard.
If you plan to use other deployment technologies, consider the following recommendations to help you successfully redistribute your application.
The following files are the minimum dependencies that are required for any simple Visual Basic 6.0 application to function:
| • | Msvbvm60.dll |
| • | Oleaut32.dll |
| • | Olepro32.dll |
| • | Asycfilt.dll |
| • | Stdole2.tlb |
| • | Comcat.dll |
If you are using Visual Studio Installer to build an installer package, these files are already included in a merge module that is added to your installer package when you build the installer package. If you are using an alternative installer technology, make sure that you redistribute these files, together with any other dependencies that your application requires.
If you want to add these files manually to your redistribution package, copy these files from the Redist folder on a computer where Visual Basic 6.0 and its latest service pack are installed. By using this method, you can make sure that your package does not include newer versions of operating system files that may cause problems during installation.
Consider building a Setup package for the application by using the Package and Deployment Wizard before you build a package by using an alternative technology. This method will help you determine what dependencies the Package and Deployment Wizard includes in its Setup package.
| 1. | Assemble a Setup package by using the Package and Deployment Wizard. | ||||
| 2. | Open the Setup.lst file, and then view the [Bootstrap Files] section and the [Setup1 Files] section for the following:
Review these lists to verify that your alternative installation package also installs these files. |
After you have followed these steps, if you are still experiencing problems when you run the deployed application, try to install the application by using the Setup package that you built by using the Package and Deployment Wizard. Then, verify that the application that you installed by using the Package and Deployment Wizard Setup package works successfully. If you cannot do this, consider troubleshooting the issue by using one of the tools that is mentioned in the “Tools for troubleshooting deployment issues” section.
For more information about third-party installers and Visual Basic applications, click the following article numbers to view the articles in the Microsoft Knowledge Base:
257773 (http://support.microsoft.com/kb/257773/) Support for third-party installers
View products that this article applies to.
| Article ID | : | 263739 |
| Last Review | : | August 30, 2004 |
| Revision | : | 3.2 |
This article was previously published under Q263739
Steps to Create a Visual Basic Installation Package
This article explains how you can use Visual Studio Installer to create a Microsoft Visual Basic installation package.
| 1. | Start Visual Studio Installer (VSI). |
| 2. | In the left side of the New Project dialog box, expand the Visual Studio folder, and then select the Visual Studio Installer Projects folder. |
| 3. | On the right side of the dialog box, select Visual Basic Installer. |
| 4. | Specify the name and location of your Microsoft Windows Installer (.msi) package in the Name and Location edit boxes, and then click Open. |
| 5. | Browse to the location of your .vbp file. |
| 6. | Select Create Installer as the setup type. |
| 7. | Click Finish. |
| 8. | Make custom changes, such as adding additional files or adding shortcuts to the project. |
| 9. | To build the project, from the Build menu, choose Build. |
For additional information about adding and registering COM Objects, click the article number below to view the article in the Microsoft Knowledge Base:
248023 (http://support.microsoft.com/kb/248023/EN-US/) How To Add and Associate COM Objects for Visual Basic Clients in Visual Studio Installer
For additional information about adding files to a VSI project, click the article number below to view the article in the Microsoft Knowledge Base:
263742 (http://support.microsoft.com/kb/263742/EN-US/) How To Add files to Visual Studio Installer Projects
For additional information about downloading the Visual Studio Installer, click the article number below to view the article in the Microsoft Knowledge Base:
269693 (http://support.microsoft.com/kb/269693/EN-US/) Visual Studio Installer Web Location
NOTE: If you would like to include the Windows Installer redistributable file with your package, see the following Microsoft Knowledge Base article:
283168 (http://support.microsoft.com/kb/283168/EN-US/) How To Install Windows Installer with Visual Studio Installer Packages
NOTE: If your application requires the installation of Microsoft Data Access Components (MDAC), click the article number below to view the article in the Microsoft Knowledge Base:
257604 (http://support.microsoft.com/kb/257604/EN-US/) FILE: Encapsulate DCOM and MDAC Installations with Windows Installer
For more information, see the Support WebCast at the following Microsoft Web site:
http://support.microsoft.com/servicedesks/Webcasts/WC081000/wcblurb081000.asp (http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fservicedesks%2fwebcasts%2fwc081000%2fwcblurb081000.asp)
Back to the top