Visual Basic Programmer

Make a standard DLL

noreply@blogger.com (Kaleng) — Wed, 06 May 2009 12:54:00 +0000

This examples builds a standard DLL that you can call by using the normal DLL calling conventions. For full details, see the article Creating a Windows DLL with Visual Basic.

Thanks to Luke Emmet for pointing this article out.

The basic staps are:

Hack the linking process.
1. Make an executable program to call the linker. Reomve the default Form1 and create the following Sub Main.

Public Sub Main()    Dim SpecialLink As Boolean, fCPL As Boolean, fResource _        As Boolean    Dim intPos As Integer    Dim strCmd As String    Dim strPath As String    Dim strFileContents As String    Dim strDefFile As String, strResFile As String    Dim oFS As New Scripting.FileSystemObject    Dim fld As Folder    Dim fil As File    Dim ts As TextStream, tsDef As TextStream     strCmd = Command        Set ts = oFS.CreateTextFile(App.Path & "\lnklog.txt")        ts.WriteLine "Beginning execution at " & Date & " " & _        Time()    ts.WriteBlankLines 1    ts.WriteLine "Command line arguments to LINK call:"    ts.WriteBlankLines 1    ts.WriteLine "   " & strCmd    ts.WriteBlankLines 2        ' Determine if .DEF file exists    '    ' Extract path from first .obj argument    intPos = InStr(1, strCmd, ".OBJ", vbTextCompare)    strPath = Mid(strCmd, 2, intPos + 2)    intPos = InStrRev(strPath, "\")    strPath = Left(strPath, intPos - 1)    ' Open folder    Set fld = oFS.GetFolder(strPath)        ' Get files in folder    For Each fil In fld.Files       If UCase(oFS.GetExtensionName(fil)) = "DEF" Then          strDefFile = fil          SpecialLink = True       End If       If UCase(oFS.GetExtensionName(fil)) = "RES" Then          strResFile = fil          fResource = True       End If       If SpecialLink And fResource Then Exit For    Next           ' Change command line arguments if flag set    If SpecialLink Then       ' Determine contents of .DEF file       Set tsDef = oFS.OpenTextFile(strDefFile)       strFileContents = tsDef.ReadAll       If InStr(1, strFileContents, "CplApplet", _           vbTextCompare) > 0 Then          fCPL = True       End If              ' Add module definition before /DLL switch       intPos = InStr(1, strCmd, "/DLL", vbTextCompare)       If intPos > 0 Then          strCmd = Left(strCmd, intPos - 1) & _                " /DEF:" & Chr(34) & strDefFile & Chr(34) & _                    " " & _                Mid(strCmd, intPos)       End If       ' Include .RES file if one exists       If fResource Then          intPos = InStr(1, strCmd, "/ENTRY", vbTextCompare)          strCmd = Left(strCmd, intPos - 1) & Chr(34) & _              strResFile & _                   Chr(34) & " " & Mid(strCmd, intPos)       End If              ' If Control Panel applet, change "DLL" extension to       ' "CPL"       If fCPL Then          strCmd = Replace(strCmd, ".dll", ".cpl", 1, , _              vbTextCompare)       End If              ' Write linker options to output file       ts.WriteLine "Command line arguments after " & _           "modification:"       ts.WriteBlankLines 1       ts.WriteLine "   " & strCmd       ts.WriteBlankLines 2    End If        ts.WriteLine "Calling LINK.EXE linker"    Shell "linklnk.exe " & strCmd    If Err.Number <> 0 Then       ts.WriteLine "Error in calling linker..."       Err.Clear    End If        ts.WriteBlankLines 1    ts.WriteLine "Returned from linker call"    ts.Close End Sub

This program does roughly the same thing that Visual Basic does when it creates a DLL except it adds the /DEF flag to the command.

Compile the executable.

Rename the normal Visual Basic linker from Link.exe to LinkLnk.exe. On my system, it's at C:\Program Files\Microsoft Visual Studio\VB98.

Copy the executable program that you compiled into this directory and name it Link.exe. When Visual Basic links the DLL, it calls this program, which calls the renamed LinkLnk.exe program, adding the new /DEF parameter.

Export the DLL's routines.

Create a file named .def where is the name of the DLL. In this example, the DLL is named Fibonacci.dll so this file is called Fibonacci.def.
Add code to this file similar to the following:

NAME MathLib LIBRARY MathMod DESCRIPTION "Add-on Library of Mathematical Routines" EXPORTS DllMain @1         Fibo @2

This tells the linker about the main entry point DllMain and this example's function Fibo, both of which are created shortly.

Build the DLL.

Create a new ActiveX DLL project.
Leave the default Class1 class alone. You will not use it but Visual Basic needs it to it has something to compile into the ActiveX DLL.
Add a code module and insert this code:

Public Const DLL_PROCESS_DETACH = 0 Public Const DLL_PROCESS_ATTACH = 1 Public Const DLL_THREAD_ATTACH = 2 Public Const DLL_THREAD_DETACH = 3  Public Function DllMain(hInst As Long, fdwReason As Long, _     lpvReserved As Long) As Boolean    Select Case fdwReason       Case DLL_PROCESS_DETACH          ' No per-process cleanup needed       Case DLL_PROCESS_ATTACH          DllMain = True       Case DLL_THREAD_ATTACH          ' No per-thread initialization needed       Case DLL_THREAD_DETACH          ' No per-thread cleanup needed    End Select End Function  ' Return a Fibonacci number. Public Function Fibo(ByVal N As Integer) As Long     If N <= 1 Then         Fibo = 1     Else         Fibo = Fibo(N - 1) + Fibo(N - 2)     End If End Function

DllMain is the DLL entry point. Fibo is a function that the DLL is exporting.

Compile the DLL. This should invoke the new Link.exe you built. If you look in that program's directory, you should see the log file it generates.

Build a test program to call the DLL.

Make a standard Visual Basic EXE.
Declare the routine exported by the DLL as in the following code:

Private Declare Function Fibo Lib _     "C:\WebSite\HowToSrc\a2\Fibonacci.dll" (ByVal N As _     Integer) As Long

Insert the path to the DLL on your computer.

Run the program.

That should do it. Watch out for typos. If the .DEF file doesn't spell the function's name correctly, the DLL won't compile and the error messages are not very good.

Creating PDF files in Visual Basic

noreply@blogger.com (Kaleng) — Wed, 29 Apr 2009 10:09:00 +0000

PDF stands for portable document format. It is a format that every operating system on virtually any computer can read. Its become the default standard for transferring and viewing files in an easy way. The problem is that Visual Basic has no built in VB6 PDF functions. Because of this it has been very hard in the past to create PDF files from VB. Hopefully by the end of this Visual Basic Tutorial, PDF creation will be an easy thing for you to understand and do first hand.

PDF is a pretty complex data format. Because, of this usually you have to buy a third party control from someone who's invested a large amount of time in navigating through the PDF format and written an easy way for you to access it. This tutorial explains how you can create a simple PDF file without a third party control. If you run into limitations down the road you might still end up having to purchase a control. However, you will then know exactly what to look for in the control and know how much you are willing to spend to get the functionality you need. Hopefully you won't even need to purchase one. If there is something you are trying to do, add a comment here or in the forum, and we will try to help you with it

Private Sub Command1_Click()
' Create a simple PDF file using the mjwPDF class
Dim objPDF As New mjwPDF

' Set the PDF title and filename
objPDF.PDFTitle = "Test PDF Document"
objPDF.PDFFileName = App.Path & "\test.pdf"

' We must tell the class where the PDF fonts are located
objPDF.PDFLoadAfm = App.Path & "\Fonts"

' View the PDF file after we create it
objPDF.PDFView = True

' Begin our PDF document
objPDF.PDFBeginDoc
' Set the font name, size, and style
objPDF.PDFSetFont FONT_ARIAL, 15, FONT_BOLD

' Set the text color
objPDF.PDFSetTextColor = vbBlue

' Set the text we want to print
objPDF.PDFTextOut _
"Hello, World! From mjwPDF (www.vb6.us)"

' End our PDF document (this will save it to the filename)
objPDF.PDFEndDoc
End Sub

From http://www.vb6.us

noreply@blogger.com (Kaleng) — Wed, 29 Apr 2009 09:59:00 +0000

Arms Trouble

noreply@blogger.com (Kaleng) — Wed, 22 Apr 2009 07:02:00 +0000

A man went to visit his doctor. "Doc, my arm hurts bad. Can you check it out please?" the man pleads.

The doctor rolls up the man's sleeve and suddenly hears the arm talk. "Hello, Doctor't; says the arm. "Could you lend me twenty bucks please? I'm desperate!"

"Aha!'' says the doctor.

''I see the problem. Your arm is broke!"

Menggunakan XP Style

noreply@blogger.com (Kaleng) — Wed, 22 Apr 2009 05:59:00 +0000

Prasetyo Priadi

prasetyopriadi@yahoo.co.id

www.PrasetyoLabs.Co.Cc

VB6 IDE

Ketik script xml berikut dalam text editor (seperti notepad) lalu simpan file tersebut

dengan nama vb6.exe.manifest.

Sudah disertakan dalam file supplemen e-book IlmuKomputer ini. (vb6xpstyle.zip) atau

Alternative Download: http://www.ziddu.com/download/2658154/vb6_manifest.zip.html

Setelah itu copy ke folder dimana visual basic 6.0 (vb6.exe) berada. Nah…, Sekarang

aktifkan aplikasi VB6 dan lihatlah IDE-nya sudah mengikuti style xp.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assemblyIdentity

version="1.0.0.0"

processorArchitecture="X86"

name="Microsoft.VB6.VBnetStyles"

type="win32"

<description>VBnet Manifest for VB6 IDE</description>

<assemblyIdentity

type="win32"

name="Microsoft.Windows.Common-Controls"

version="6.0.0.0"

processorArchitecture="X86"

publicKeyToken="6595b64144ccf1df"

language="*"

</dependentAssembly>

</dependency>

</assembly>

Komunitas eLearning IlmuKomputer.Org

VB6 Project

Style Menggunakan XML

Project Folder: vb6xpxmlext

Jika sebelum Anda memasuki bab perihal pembahasan ini, yaitu dengan nekat telah mencopy

vb6.exe.manifest tadi ke folder project Anda dan me-rename-nya menjadi

project1.exe.manifest yang disandingkan dengan program Anda (project1.exe). Maka

secara otomatis file hasil compile-an tadi ngambek dan pastinya tidak mau jalan.

Speaker Anda mungkin hanya akan berbunyi (teeng, teeng) setiap berulang kali Anda

mencoba mengaktifkan program project1.exe Anda dan tidak tampil apa-apa. Lebih

buruk lagi muncul kotak dialog: error, please reinstall this program and bla…bla. bla..

Coba tebak apa yang salah? Yup.., benar XP Manifest tadi belum di inisialisasikan. Lalu

bagaimanakah cara membuat kode untuk menginisialisasikannya? Ya.. ya.. itu cukup

mudah. Tinggal ikuti prosedur dibawah ini.

1. Bukalah proyek baru menggunakan Standar.Exe.

2. Double klik Form1, dan ketikan kode berikut pada halaman kode.

3. Dari menu utama pilih menu Project _ Add Module. Pada kotak dialog Add

Module klik tombol Open. Atau dengan double klik icon Module.

4. Pada halaman kode Module1 ketikan kode berikut ini.

5. Kembali ke Form1, tambahkan sebuah objek command button.

Private Sub Form_Initialize()

InitCommonControls

End Sub

Public Declare Function InitCommonControls Lib "COMCTL32.DLL" _

() As Long

6. Compile project Anda.

7. Pastikan Anda sudah membuat project1.exe.manifest pada folder hasil compile. Nama

manifest yaitu mengikuti nama executable hasil kompilasi misal program Anda

Aqua.exe maka nama manifest-nya adalah Aqua.exe.manifest.

8. Jalankan program. Lihatlah program berjalan dengan normal dan tentunya dengan

style XP, atau style theme xp yang sedang Anda gunakan.

VB6 Project

Style Menggunakan XML Autowrite

Project Folder: vb6xpxmlxto

Apabila Anda diserang badai kemalasan, untuk men-copy file manifest ke setiap folder

project Anda atau barangkali untuk menangulangi file manifest di hapus oleh pengguna

program kita. Maka, bisa Anda gunakan module xpmanifest.bas (sudah saya modifikasi

sedikit agar setiap selesai inisial xp style maka file bla..bla..bla.exe.xpmanifest akan

secara otomatis dihapus).

Loh apa ndak sulit buatnya? Tidak kok, tinggal ikuti saja.

1. Bukalah proyek baru menggunakan Standar.Exe.

2. Double klik Form1, dan ketikan kode berikut pada halaman kode.

Private Sub Form_Initialize()

xpManifestInitial

End Sub

3. Dari menu utama pilih menu Project _ Add Module. Pada kotak dialog Add

Module klik tombol Open. Atau dengan double klik icon Module.

4. Pada halaman kode Module1 ketikan kode berikut ini.

'XP Manifest for visual basic 6.0

'Type External Autowrite & Stleath

Private Type tagInitCommonControlsEx

lngSize As Long

lngICC As Long

End Type

Private Declare Function InitCommonControlsEx Lib "comctl32.dll"

(iccex As tagInitCommonControlsEx) As Boolean

Private Const ICC_USEREX_CLASSES = &H200

Public Sub xpManifestInitial()

On Error Resume Next

Dim F As String

F = App.Path & "\" & App.EXEName & ".exe.manifest"

If Dir(F) = "" Then

Open F For Output As #3

Print #3, "<?xml version=" & Chr(&H22) & "1.0" & _

Chr(&H22) & " encoding=" & Chr(&H22) & "UTF-8" & _

Chr(&H22) & " standalone=" & Chr(&H22) & "yes" & _

Chr(&H22) & " ?>"

Print #3, "<assembly xmlns=" & Chr(&H22) & _

"urn:schemas-microsoft-com:asm.v1" & Chr(&H22) & _

" manifestVersion=" & Chr(&H22) & "1.0" & Chr(&H22) & ">"

Print #3, vbTab & "<assemblyIdentity"

Print #3, vbTab & vbTab & "version=" & Chr(&H22) & _

"1.0.0.0" & Chr(&H22)

Print #3, vbTab & vbTab & "processorArchitecture=" & _

Chr(&H22) & "X86" & Chr(&H22)

Print #3, vbTab & vbTab & "name=" & Chr(&H22) & _

App.CompanyName & "." & App.ProductName & "." & _

App.EXEName & Chr(&H22)

Print #3, vbTab & vbTab & "type=" & Chr(&H22) & _

"win32" & Chr(&H22) & " />"

Print #3, vbTab & "<description>" & App.Comments & _

"</description>"

Print #3, vbTab & "<dependency>"

Print #3, vbTab & "<dependentAssembly>"

Print #3, vbTab & "<assemblyIdentity"

Print #3, vbTab & vbTab & "type=" & Chr(&H22) & _

"win32" & Chr(&H22)

Print #3, vbTab & vbTab & "name=" & Chr(&H22) & _

"Microsoft.Windows.Common-Controls" & Chr(&H22)

Print #3, vbTab & vbTab & "version=" & Chr(&H22) _

& "6.0.0.0" & Chr(&H22)

Print #3, vbTab & vbTab & "processorArchitecture=" & _

Chr(&H22) & "X86" & Chr(&H22)

Print #3, vbTab & vbTab & "publicKeyToken=" & _

Chr(&H22) & "6595b64144ccf1df" & Chr(&H22)

Print #3, vbTab & vbTab & "language=" & Chr(&H22) & _

"*" & Chr(&H22) & " />"

Print #3, vbTab & "</dependentAssembly>"

Print #3, vbTab & "</dependency>"

Print #3, "</assembly>"

Print #3, ""

Close #3

Shell App.Path & "\" & App.EXEName & ".exe", vbNormalFocus

DoEvents

End

End If

5. Kembali ke Form1, tambahkan sebuah objek command button.

6. Compile project Anda. Jalankan dan lihatlah hasilnya. Dengan cara ini Anda tak perlu membuat file manifest dengan cara manual karena file

manifest akan dibuat dan kemudian di hapus oleh program. Lebih tepatnya pada sub xpManifestInitial yang dipanggil pada Form_Initialize().

VB6 Project

Style Menggunakan Resource

Project Folder: vb6xpxmlres

Jika boleh berkata jujur, sebenarnya saya tahu cara ini saat sebelum mendekompilasi

program "123 Flash Compressor" menggunakan VBReformer. Pertama saya lihat

program tersebut dengan PEiD ternyata diketahui program tersebut ditulis menggunakan

VB6. Saya lihat stylenya kok memakai XP, tetapi tidak ada file manifest-nya. Saya

berpikir, barangkali menggunakan resource dan ternyata benar saat saya buka dengan

Resource Hacker. Langsung saja saya klik menu Action _ Save Resource As a *.res

File. Saya coba di VB6 tentunya dengan inisialisasi komponen comctl32.dll dan berhasil.

Dim Ticce As tagInitCommonControlsEx

Ticce.lngSize = LenB(iccex)

Ticce.lngICC = ICC_USEREX_CLASSES

InitCommonControlsEx Ticce

Kill App.Path & "\" & App.EXEName & ".exe.manifest"

On Error GoTo 0

End Sub

Langkah-langkah cara membuatnya adalah sebagai berikut.

1. Bukalah proyek baru menggunakan Standar.Exe.

2. Double klik Form1, dan ketikan kode berikut pada halaman kode.

3. Dari menu utama pilih menu Project _ Add Module. Pada kotak dialog Add

Module klik tombol Open. Atau dengan double klik icon Module.

4. Pada halaman kode Module1 ketikan kode berikut ini.

5. Dari menu utama pilih menu Project _ Add File… (Ctrl + D). Cari file

xpmanifest.res (sudah disertakan dalam file supplement e-Book ini).

6. Kembali ke Form1, tambahkan sebuah objek command button.

7. Compile project Anda.

8. Jalankan program. Lihatlah program berjalan dengan normal dan tentunya dengan

style XP, atau style theme xp yang sedang Anda gunakan.

Dengan cara ini Anda tak lagi perlu membuat xpmanifest secara manual ataupun secara

automatis menggunakan kode program, karena xpmanifest telah tersedia sebagai resource

dengan nama file xpmanifest.res.

Private Sub Form_Initialize()

InitCommonControls

End Sub

Public Declare Function InitCommonControls Lib "COMCTL32.DLL" _

() As Long

VB6 Project

Style Menggunakan XML

Project Folder: vb6xpvoodo

Dengan menggunakan module ModXP.bas yang ditulis oleh Voodoo Attack!!. Kita dapat

menggunakan XP Style tidak hanya untuk aplikasi yang ditulis dengan Visual Basic 6.0

tetapi juga Visual Basic 5.0

Cara membuatnya adalah sebagai berikut.

1. Bukalah proyek baru menggunakan Standar.Exe.

2. Double klik Form1, dan ketikan kode berikut pada halaman kode.

3. Dari menu utama pilih menu Project _ Add Module. Klik tab Existing . Carilah file

ModXP.bas (sudah disertakan dalam file supplemen e-Book ini). Dan klik open.

4. Kembali ke Form1, tambahkan sebuah objek command button.

5. Compile project Anda.

6. Jalankan program. Lihatlah program berjalan dengan normal dan tentunya dengan style XP, atau style theme xp yang sedang Anda gunakan. ModXP.bas XPStyle Module yang saya pergunakan adalah versi 2.00

Private Sub Form_Initialize()

XPStyle

End Sub

E-Book Gratis dengan Bahasa indonesia

noreply@blogger.com (Kaleng) — Wed, 22 Apr 2009 03:11:00 +0000

Teman-teman programmer VB 6 maupun pemula di VB 6.
Saya menemukan beberapa Ebook gratis untuk Tutorial Basic Programmer ataupun Expert Programmer.

Berikut Link-link Ebook tersebut:

Saya akan sambung lagi jika ada yang baru.

Get disk serial number using the file system object

noreply@blogger.com (Kaleng) — Mon, 23 Feb 2009 06:54:00 +0000

Description: This VB code (function) enables you to retrieve the hard disk (partition) serial number. This serial number is generated by Windows (or DOS) when you format a disk partition.

Keywords: Disk Serial Number, Hard Disk Serial, Drive Serial Number 'Note: This code requires a referecne to the Microsoft Scripting Runtime library (SCRRUN.DLL)

Private Sub Form_Load()
'Show drive serial number for the current drive
MsgBox " Drive serial number for " & Left(App.Path, 1) & ": " & GetDriveSerialNumber
End
End Sub

Public Function GetDriveSerialNumber(Optional ByVal DriveLetter As String) As Long
Dim fso As Object, Drv As Object
'Create a FileSystemObject object
Set fso = CreateObject("Scripting.FileSystemObject")

'Assign the current drive letter if not specified
If DriveLetter <> "" Then
Set Drv = fso.GetDrive(DriveLetter)
Else
Set Drv = fso.GetDrive(fso.GetDriveName(App.Path))
End If

With Drv
If .IsReady Then
DriveSerial = Abs(.SerialNumber)
Else '"Drive Not Ready!"
DriveSerial = -1
End If
End With

'Clean up
Set Drv = Nothing
Set fso = Nothing

GetDriveSerialNumber = DriveSerial
End Function

noreply@blogger.com (Kaleng) — Mon, 25 Aug 2008 02:20:00 +0000

Apa itu ERP ? Apa yang dapat dilakukan ERP ?

Enterprise Resource Planning yang lebih di kenal ERP , kalau kita artikan secara kata per kata dan coba di cari di kamus adalah sebagai berikut:

Enterprise à
plural: enterprises Arti : keberanian berusaha, kegiatan memulai usaha
Resource à
plural: resources Arti: akal, sumber, sumber penghasilan
Planning à
present: plans. present participle: planning Arti: merencanakan, rencana, perencanaan, berencana

Jika dirangkaikan adalah "Rencana Sumber Penghasilan" ? atau "Rencana Untuk Membuat Sumber Pengahasilan"? atau "Merencanakan Sumber Penghasilan"?? ga Nyambung!!

berbeda jauh artinya dengan sebenar nya. Gua coba juga bertanya dengan teman sekerja di kantor" apa sih ERP ?" . Ada banyak jawaban seperti " ERP itu aplikasi (Software)" dan ada lagi " ERP itu punya orang IT dan sulit sekali".
gw juga mencoba mencari definisi yang tepat dengan cari di artikel , internet dan text book tapi semua nya memberikan definisi yang berbeda dengan berbagai sudut pandang tapi dapat secara garis besar mempunyai arti hampir sama.
ERP itu merupakan sistim terintegrasi yang mempunyai tujuan merangkum bisnis proses yang ada sehingga menjadi satu kolaborasi yang effisien dan effektif dan sistim tersebut di dukung dengan teknologi informasi dan dapat menghasilkan informasi yang menunjang perusahaan menjadi lebih kompetitif.
Berikut contoh yang dapat ERP lakukan seperti dalam kasus di produksi . dimana antara jadwal produksi dengan bahan yang ada dan kebutuhan produk yang akan diproduksi dimana ketiga proses itu harus dilakukan secara effisien dan effektif. contoh effisien adalah dari segi waktu dan effektif dari segi optimasi dalam proses produksi dimana sebagai contoh meminimalkan WIP. Ini hanya sebagian contoh dari salah satu tugas ERP.

Critical Succes Factor untuk implemantasi ERP

Sukses adalah hasil dari suatu strategi dan usaha , tidak datang dengan kebetulan . suskes dalam meng ' Go Live' ERP juga perlu strategi dan usaha . banyak tulisan mengenai critical succes factor untuk mengimplementasikan sebuah enterprise system. saya coba melihat salah satu artikel yg ditulis oleh Anne Parr dan Graeme Shanks di Jurnal of Information Technology (2000) 15 . Didalam jurnal tersebut point - point Critical Success Factor (CSF) untuk implementasi ERP adalah :

Management support, dukungan dan komitmen dari top management sangat di butuhkan dari sebelum project dimulai sampai setelah project selesai atau sudah . kenapa saya menuliskan sampai setelah project selesai , ini di perlukan agar semangat pengembangan dan ke ikut sertaan dari semua yg terlibat terus berakar.
Keterlibatan orang - orang yg berkompeten dalam bidang nya secara full time .Kenapa harus full time yaitu agar lebih fokus.
Diberikan wewenang untuk memberikan keputusan, wewenang disini berarti di berikan nya delegasi untuk dapat memutuskan sehingga keputusan yang akan lebih cepat tapi harus dilakukan oleh orang yang kompeten.
Delivered date, Jadwal yang realisitis dan tetap harus selalu di monitor perkembangan dan kemajuannya
Champion, agen perubahan dimana selalu ber ' promosi ' mengenai sistem yang baru dan bertugas untuk sebagai 'pendengar' sehingga menjadi koreksi dalam implementasi.
Vanila ERP, istilah saja agar implementasi ERP hanya melakukan sedikit Customize. kenapa sedikit karena untuk memudahkan upgarade software.
Ruang lingkup yang tidak terlalu besar, sangat baik dilakukan dengan ruang lingkup yg tidak terlalu besar dahulu agar lebih effektif & effisien . Hindari "Big Bang" project
Definisi tujuan dan ruang lingkup, ini salah satu terpenting karena Steering Committee mendefinisikan tujuan & ruang lingkup yang jelas. ini sebenar nya merupakan inti dari mau kemana kita nanti nya. ini semua harus benar - benar di pahami oleh seluruh anggota project. Apabila gagal mendifinisikan secara benar maka biasa nya project akan menjadi terlambat dan akhir nya ujung - ujung nya cost nya juga naik
Komposisi team yang seimbang, komposisi yang seimbang dari bisnis analis, technical expert dan user yang ikut dalam implementasi dari internal dan external perusahaan
Commitment to change, ketekunan dan ketabahan dalam menghadapi masalah yang terjadi selama implementasi.

Letter from Banta Singh to Bill Gates

noreply@blogger.com (Kaleng) — Wed, 16 Jul 2008 10:38:00 +0000

Subject: Problems with my new computer

Dear Mr Bill Gates,
We have bought a computer for our home and we have found some problems, which I want to bring to your notice

1. There is a button 'start' but there is no 'stop' button. We request you to check this.
2. We find there is 'Run' in the menu. We request you to change that to 'sit', so that we can click that by sitting.
3. One doubt is whether any 're-scooter' is available in system? I find only 're-cycle', but I own a scooter at home.
4. There is 'Find' button but it is not working properly. My wife lost the door key and we tried a lot trace the key with this ' find' button, but was unable to trace. Please rectify this problem.
5. My child learnt 'Microsoft word' now he wants to learn 'Microsoft sentence', so when you will provide that?
6. I bought computer, CPU, mouse and keyboard, but there is only one icon which shows 'My Computer'; when you will provide the remaining items?
7. It is surprising that windows says 'My Pictures' but there is not even a single photo of mine. So when will you keep my photo in that.
8. There is 'Microsoft Office' what about 'Microsoft Home'? since I use the PC at home only.
9. You provided 'My Recent Documents'. When you will provide 'My Past Documents'?
10. You provide 'My Network Places'. For God Sake! Please do not provide 'My Secret Places'. I do not want to let my wife know where I go after my office hours.

Regards,
Banta Singh

Last one to Mr Bill Gates :
Sir, how is it that your name is Gates but you are selling WINDOWS?

noreply@blogger.com (Kaleng) — Wed, 16 Jul 2008 07:20:00 +0000

This article originally appeared in the Builder.com Visual Basic e-newsletter. Click here to subscribe automatically.

A user defined type, or UDT, is a VB technique for defining a data type that exactly meets the needs of your program. A UDT can contain two or more individual data items that can be of different types, such as String and Integer. A UDT can even contain other UDTs and arrays. You can also create arrays of a UDT.

To define a UDT, use the Type...End Type statement, which must appear in the declarations section of a code module. Within the statement, you define the individual items, or members, that the UDT will contain.

Here's an example of a UDT you might create for keeping track of employee data:

Public Type Employee
    FirstNameAs String
    LastName As String
    DateOfHire As Date
    Salary As Currency
    EmployeeNumber As Integer
End Type

Once you define the type, you can create instances of it just like any other data type, like so:

Dim OneEmployee As Employee
Dim AllEmployees(500) As Employee

To access the members of a UDT, you use the Name.Member notation. Here are some examples:

OneEmployee.FirstName = "Jack"
OneEmployee.LastName = "Sprat"
AllEmployees(1).FirstName = "Maria"
AllEmployees(1).LastName = "Sanchez"

Nesting UDTs can be useful in some situations. Here's an example:

Public Type Person
    FirstNameAs String
    LastName As String
End Type
Public Type Employee
    Name As Person
    DateOfHire As Date
    Salary As Currency
    EmployeeNumber As Integer
End Type

When UDTs are nested, you use the same Name.Member notation but with an extra level, like this:

Dim OneEmployeeAs Employee
OneEmployee.Name.FirstName = "Jack"

You can also use UDTs for arguments to functions and procedures and as the return type for functions. They can also be helpful when storing data on disk because VB's Random file type is specifically designed to work with UDTs.

All in all, UDTs are a tool that every VB programmer should know about.

Peter Aitken has been programming with Visual Basic since Version 1.0. He has written numerous books and magazine articles on Visual Basic and other computer and programming topics.

Pass strings ByRef

noreply@blogger.com (Kaleng) — Thu, 29 May 2008 03:34:00 +0000

Use ByRef instead of function return value

There's also an optimization trick for returning a string value. Returning a string as the function return value is the normal practice. However, returning a string in a ByRef parameter is faster.

The ByRef trick for return values applies to both functions and Property Get's. Here's the usual (and slower) way:

' Slow:
Property Get Name() As String
   Name = m_sName
End Property
' Slow:
Function Name() As String
   Name = m_sName
End Function

This way is faster if you have to make a large number of calls:

' Fast:
Sub GetName(ByRef Name_out As String)
   Name_out = m_sName
End Sub

It's often considered bad programming style to return values in parameters. Normally procedures should not cause side-effects by modifying their ByRef parameters. However, if you want speed, you sometimes have to reject accepted programming practices to win a few CPU cycles. Thus, the optimization objective might justify the loss of style. You can use ByRef, but you should indicate why you're using it. For example, you can mark all output parameters with the string out, or write a comment saying ByRef is used for speed.

Stick to ByVal for out-of-process calls

There is one case where ByRef is slower than ByVal. This happens when passing ByRef to an out-of-process server. The variable has to be marshalled twice, once going into the method and once returning. The implication is to use ByVal for your public server interfaces.

Comparing a character in the middle of a string

noreply@blogger.com (Kaleng) — Thu, 29 May 2008 03:24:00 +0000

Similar to the above trick, this is the way to check for a
character in the middle of a string.

If AscW(Mid$(Text$, index)) = 65 Then

Note that index must be less than or equal to Len(Text$), otherwise you get a run-time error. In this case, call Mid$(, index) instead of Mid$(, index, 1). The third parameter (length) actually makes the call slower, although one could assume the opposite.

Compare in binary

PA Whenever you can, use binary comparison. This is VB's default. Text comparison is much slower. These statements slow your application down:

Option Compare Text
StrComp(, , vbTextCompare)
InStr(, , , vbTextCompare)

If you need a case-insensitive StrComp(), use LCase$ to do it,
especially if it's enough on one parameter only:

StrComp(Text1$, "abc", vbTextCompare)           ' Slower
StrComp(LCase$(Text1$), "abc", vbBinaryCompare) ' Faster

In the following case, the two calls to LCase$ remove the performance gain you got above.

StrComp(LCase$(Text1$), LCase$(Text2$), vbBinaryCompare)

Bear in mind that StrComp(,,vbTextCompare) is more than just a case-insensitive comparison. It's actually built for sorting, not comparing for equality. In many cases, such a locale-dependent
textual comparison is an overkill and can even lead to subtle errors.

Check for existence with InStrB

InStr is a nice function to find a string inside another one. Normally you use the plain InStr function, the wide-character version.

There is an optimization with the byte version (InStrB). If you are just going to check whether a string exists inside the other but don't care about the location, you can use the following code:

If InStrB(Text$, SearchFor$) <> 0 Then

Since you only compare the return value against zero, you don't need to worry about conversions between byte-based indices and character indices. This is not the whole story, however. You need to be aware of the following catches:

InStrB works completely on byte-based index values. The return value, as well as the start index parameter (the first numeric parameter, not present in the above call) are both in
bytes, not in characters. One character is 2 bytes.
Use the equation byteindex = (characterindex * 2) - 1 to convert indices.
If there is a match at character 3, the byte index is 5.

InStrB is a byte data function and it's dangerous to use it on character input. If the strings may contain character values outside the range 1-255, be careful. Chances are InStrB is not good for you. As InStrB does a byte-wise search, it can return matches between characters:
```
Text$ = ChrW$(&H1234) & ChrW$(&H5678) ' Bytes 34 12 78 56 hex
SearchFor$ = ChrW$(&H7812)            ' Bytes    12 78 
```
In this case, InStrB returns 2, which is the start of the byte sequence 12 78 but doesn't match any of the input characters. This is probably not what you want when working with strings. Note that even if your strings are plain ASCII, the null character can still pose a problem (for example, InStrB("A" & vbNullChar, vbNullChar) returns 2, not 3 as you could expect).
There are extra complications with the vbTextCompare parameter. vbBinaryCompare is simpler to understand.

What does this mean? Use InStrB to optimize only when you fully understand how it works.

Like

The Like operator is not particularly fast. Consider alternatives. We don't have a generic rule to follow here. You need to measure the performance differences between your alternatives.
Here is one rule though. It applies if you're looking for a certain string inside another one.

Instead of:
 If Text$ Like "*abc*" Then

Use:
 If InStr(Text$, "abc") <> 0 Then

You may also use InStrB if you know what you're doing.

Comparing the leftmost character

noreply@blogger.com (Kaleng) — Thu, 29 May 2008 03:21:00 +0000

Here are two unoptimized ways to branch on the first character in
a string.

' Case 1
If Left$(Text$, 1) = "A" Then

' Case 2
Select Case Left$(Text$, 1)
   Case "A"
   Case "B"
End Select

Here are the faster alternatives.

' Case 1
If LenB(Text$) <> 0 Then
   If AscW(Text$) = 65 Then

' Case 2
If LenB(Text$) <> 0 Then
   Select Case AscW(Text$)
      Case 65 ' AscW("A")=65
      Case 66
End Select

Calling AscW() is faster than first calling Left$(), then comparing the result to another string. There's a caveat, however. AscW() on an empty or null string is a run-time error. That's why
you must call LenB() first to rule out that possibility. You can leave out the call to LenB() only if you're certain that the string contains at least one character.

The Select Case structure offers an additional bonus. Having single numbers in the Case conditions is less time-intensive than repeatedly comparing against a string.

Built-in string constants

noreply@blogger.com (Kaleng) — Thu, 29 May 2008 03:11:00 +0000

vbNullChar     0
vbBack         8
vbTab          9
vbLf          10
vbVerticalTab 11
vbFormFeed    12
vbCr          13
vbCrLf        13+10
vbNewline     13+10
""            34

For some reason, vbNewline is a little bit faster than vbCrLf.

The last example ("") is not actually a constant but an escape sequence. You can use "" anywhere in a string to represent a quotation mark. The alternative is Chr(34), which was required in some early BASIC versions where the "" syntax didn't exist.

You can also define other other character values to avoid repeated calls to Chr$()/ChrW$(). If the character value is in the range ASCII 0-31, you need to define them as variables and assign the correct character value before use.

Dim BEL As String
BEL = ChrW$(7) ' The BEL character, or ^G

For other characters you can simply use a constant.

Const Percentage = "%"

Unnecessary Asc/AscW

Project Analasys It's obvious, but calling Asc/AscW on a string
constant makes no sense, as the value returned never changes. Instead of Asc("A"),
use the value 65. Better yet, define a constant such as

Const ascA = 65

and use it instead of 65 for more legibility. As it happens, VB.NET compiles Asc("A") better, but since we're in VB6, we need to define this constant.

Your own string constants

If the same string exists in more than one location in your project, it will also exist in several locations in the executable file, as far as VB6 is concerned (VB.NET joins duplicated strings during compilation).

You can optimize by defining your strings as constants and referencing the constant where you need the string value. This way you save space as each constant gets stored only once. Besides, if you ever consider localizing your program, you have a useful list of string constants to give to the translator.
There is a nasty exception. It doesn't save any space to define constants by other constants.

Const MSG1 = "Hello, "
Const MSG2 = "world!"
Const MSG3 = MSG1 & MSG2

In this case you will actually the same text twice in the executable. All of MSG1, MSG2 and MSG3 will get stored - not something you wanted to achieve! If you want to save space, concatenate MSG1 & MSG2 at run-time. For speed, store it in a variable for reuse.

Also notice that the above applies to string constants only. Numeric constants are also computed and stored in the executable, but string constants are more likely to demand more space (6 bytes overhead + 2 bytes per character).

String literal analysis is a Project Analyzer feature that reports duplicate strings. Follow the link to read more about the elimination of unnecessary string literals.

Replace or not?

noreply@blogger.com (Kaleng) — Thu, 29 May 2008 03:07:00 +0000

The following tip might be obvious, but it wasn't to us. It makes no sense to call Replace if you're not likely to replace anything. If a replace is unlikely, verify first (with InStr or InStrB, for example) that there is something you need replace.

If InStr(Text$, ToBeReplaced$) <> 0 Then
   Text$ = Replace(Text$, ToBeReplaced$, "xyz")
End If

If a replace is likely or certain to occur, there is no need to call InStr. It will just add an extra burden. Notice that it's not necessary to add $ in the call to Replace. This is an exception to the $ rule, presented above.

Use the wide AscW and ChrW$

Every string is in Unicode, which it takes 2 bytes per character.You don't have to be writing international applications to take advantage of a couple of Unicode tricks. Consider the following functions: Asc(), Chr$().
What's wrong with them?
They are the slower versions. If you're concerned about speed, use the wide versions instead: AscW(), ChrW$().

AscW() is not the same as Asc(). They return different values. ChrW$() is different from Chr$() because they take different parameter values. However, AscW() equals Asc() and ChrW$() equals Chr$() when working with characters from ASCII/Ansi 0 to 127.

Dollars that make your program run faster

noreply@blogger.com (Kaleng) — Thu, 29 May 2008 02:55:00 +0000

No variants please

It's a simple thing but often overlooked. All variables, parameters and functions should have a defined data type. If the data is a string, then the data type should be defined as string. If you don't give a data type, you're using a variant. The variant data type has its uses but not in string
processing.
A variant means performance loss in most cases.

Dollars that make your program run faster

The following functions unoptimal if you're using them on strings.

Left(), Mid(), Right(), Chr(), ChrW(),
UCase(), LCase(), LTrim(), RTrim(), Trim(),
Space(), String(), Format(), Hex(), Oct(),
Str(), Error

These are the dreaded variant functions. They take a variant, they return a variant. These functions are OK to use if you're processing variants. This is the case in database programming, where your input may contain Null values.
So what's all that variant stuff in string processing? It's fat. If you're dealing with strings, forget about the variants. Use the string versions instead:

Left$(), Mid$(), Right$(), Chr$(), ChrW$(),
UCase$(), LCase$(), LTrim$(), RTrim$(), Trim$(),
Space$(), String$(), Format$(), Hex$(), Oct$(),
Str$(), Error$

Optimize the empty string

noreply@blogger.com (Kaleng) — Thu, 29 May 2008 02:45:00 +0000

Is the "" expression often found in your code? Beware! So many CPU cycles are wasted for such a string! Testing and assigning empty strings is an easy place for optimization.

Checking for empty string

The usual ways are these:

If Text$ = "" Then
If Text$ <> "" Then

However, VB executes the following equivalent statements much faster.

If LenB(Text$)= 0 Then
If LenB(Text$)<> 0 Then

The replacement is essentially risk-free. Your code executes the same as
before, only faster.
VB's implementation of LenB is fast. LenB is the byte equivalent of Len. Len is actually implemented as LenB\2. That makes LenB is faster than Len, so you
should use it where possible. VB3 and VB.NET don't have the LenB alternative, in these languages you should use Len.

Note that we use the <> operator, not >. <> simply tests for inequality,
while > tests more. As Len/LenB never return a negative number, we can safely
use this test.

How to take a DSN Driver With VB?

noreply@blogger.com (Kaleng) — Wed, 28 May 2008 03:48:00 +0000

Make 2 Combo box in New Form.

· Named First Combo with CBODSNList
· Second Combo CBODrivers
coding an API function And Constanta:

Private Declare Function SQLDataSources Lib "ODBC32.DLL" (ByVal
henv&, ByVal fDirection%, ByVal szDSN$, _

ByVal cbDSNMax%, pcbDSN%, ByVal
szDescription$, ByVal cbDescriptionMax%, pcbDescription%) As Integer

Private Declare Function SQLAllocEnv% Lib "ODBC32.DLL" (env&)

Const SQL_SUCCESS As Long = 0
Const SQL_FETCH_NEXT As Long = 1

In Event Form Load Type in Code Under:

Private Sub Form_Load()
Dim i As Integer
Dim sDSNItem As String * 1024
Dim sDRVItem As String * 1024
Dim sDSN As String
Dim sDRV As String
Dim sDRVold As String
Dim iDSNLen As Integer
Dim iDRVLen As Integer
Dim lHenv As Long
If SQLAllocEnv(lHenv) <> -1 Then
Do Until <> SQL_SUCCESS
sDSNItem = Space$(1024)
sDRVItem = Space$(1024)
i = SQLDataSources(lHenv, SQL_FETCH_NEXT, sDSNItem, 1024, iDSNLen, sDRVItem, 1024, iDRVLen)
sDSN = Left$(sDSNItem, iDSNLen)
sDRV = Left$(sDRVItem, iDRVLen)
If sDSN <> Space(iDSNLen) Then
If UCase(Left(sDSN, 4)) = "KIS_" Then
CBODSNList.AddItem sDSN
If sDRVold <> sDRV Then
CBODrivers.AddItem sDRV
End If
sDRVold = sDRV
End If
End If
Loop
End If

If CBODrivers.ListCount > 0 Then
CBODrivers.ListIndex = 0
CBODSNList.ListIndex = 0
End If
End Sub

Finish

Click Picture to largest

Mengambil DSN Dan Driver Di ODBC(With Bahasa)

noreply@blogger.com (Kaleng) — Wed, 28 May 2008 02:57:00 +0000

Bagimana cara mengambil DSN beserta Drivernya di ODBC dengan Visual
Basic 6.00.

Masukan Dua Combo Box di form baru. Combo box 1 namanya CBODSNList Combo
box kedua namanya CBODrivers

Masukan Fungsi API di Form kyak dibawah:

Private Declare Function SQLDataSources Lib "ODBC32.DLL" (ByVal
henv&, ByVal fDirection%, ByVal szDSN$, _

ByVal cbDSNMax%, pcbDSN%, ByVal
szDescription$, ByVal cbDescriptionMax%, pcbDescription%) As Integer

Private Declare Function SQLAllocEnv% Lib "ODBC32.DLL" (env&)

Const SQL_SUCCESS As Long = 0

Const SQL_FETCH_NEXT As Long = 1

Trus Di Event Form Load masukin coding di bawah ini:

Private Sub Form_Load()

Dim i As Integer

Dim sDSNItem As String * 1024

Dim sDRVItem As String * 1024

Dim sDSN As String

Dim sDRV As String

Dim sDRVold As String

Dim iDSNLen As Integer

Dim iDRVLen As Integer

Dim lHenv As Long

If SQLAllocEnv(lHenv) <> -1 Then

Do Until i <> SQL_SUCCESS

sDSNItem =
Space$(1024)

sDRVItem =
Space$(1024)

i =
SQLDataSources(lHenv, SQL_FETCH_NEXT, sDSNItem, 1024, iDSNLen, sDRVItem,
1024, iDRVLen)

sDSN =
Left$(sDSNItem, iDSNLen)

sDRV =
Left$(sDRVItem, iDRVLen)

If sDSN <>
Space(iDSNLen) Then

If UCase(Left(sDSN, 4)) = "KIS_" Then

CBODSNList.AddItem sDSN

If sDRVold <> sDRV Then

CBODrivers.AddItem sDRV

End If

sDRVold = sDRV

End If

End If

Loop

End If

If CBODrivers.ListCount > 0 Then

CBODrivers.ListIndex = 0

CBODSNList.ListIndex = 0

End If

End Sub

Selesai

Sejarah(with bahasa)

noreply@blogger.com (Kaleng) — Tue, 27 May 2008 06:10:00 +0000

Bill Gates, pendiri Microsoft, memulai bisnis softwarenya dengan mengembangkan interpreter bahasa Basic untuk Altair 8800, untuk kemudian ia ubah agar dapat berjalan di atas IBM PC dengan sistem operasi DOS. Perkembangan berikutnya ialah diluncurkannya BASICA (basic-advanced) untuk DOS. Setelah BASICA, Microsoft meluncurkan Microsoft QuickBasic dan Microsoft Basic (dikenal juga sebagai Basic Compiler).
Sejarah BASIC di tangan Microsoft sebagai bahasa yang diinterpretasi (BASICA) dan juga bahasa yang dikompilasi (BASCOM) membuat Visual Basic diimplementasikan sebagai gabungan keduanya.
Programmer yang menggunakan Visual Basic bisa memilih kode terkompilasi atau kode yang harus diinterpretasi sebagai hasil executable dari kode VB. Sayangnya, meskipun sudah terkompilasi jadi bahasa mesin, DLL bernama MSVBVMxx.DLL tetap dibutuhkan. Namun karakteristik bahasa terkompilasi tetap muncul (ia lebih cepat dari kalau kita pakai mode terinterpretasi).

[sunting] Pemrograman Berorientasi Objek (OOP)
Visual Basic merupakan bahasa yang mendukung OOP, namun tidak sepenuhnya. Beberapa karakteristik obyek tidak dapat dilakukan pada Visual Basic, seperti Inheritance tidak dapat dilakukan pada class module. Polymorphism secara terbatas bisa dilakukan dengan mendeklarasikan class module yang memiliki Interface tertentu. Visual Basic (VB) tidak bersifat case sensitif.

[sunting] Desain Visual dan Komponen
Visual Basic menjadi populer karena kemudahan desain form secara visual dan adanya kemampuan untuk menggunakan komponen-komponen ActiveX yang dibuat oleh pihak lain. Namun komponen ActiveX memiliki masalahnya tersendiri yang dikenal sebagai DLL hell. Pada Visual Basic .NET, Microsoft mencoba mengatasi masalah DLL hell dengan mengubah cara penggunaan komponen (menjadi independen terhadap registry).

Sample code

noreply@blogger.com (Kaleng) — Tue, 27 May 2008 05:55:00 +0000

Here are some examples of the language:

Program to display a pop-up message box with the words "Hello World" on it:
Private Sub Form_Load()
MsgBox "Hello World"
End Sub

Program to display an input box:
Sub Main()
Dim a As String a = InputBox("Enter your name:")
MsgBox a
End Sub

Running Another Application Using Visual Basic:
Private Sub Run_Notepad()
Shell "notepad.exe", vbMinimizedFocus
'This would open Notepad, as Notepad is in the system folder.
'%SystemRoot% is an environment variable containing the path to the system folder.
'which is not needed as it is already in the system folder
End Sub

Printing multiplication table of 5 on form:
Private Sub PrintMul_Click()
Dim I As Integer
For I = 1 To 10
Print 5; " x "; I; " = "; 5 * I
Next I
End Sub

Displaying all prime numbers below 1,000,000:
Private Sub DisplayPrimeNumbers()
Dim Num As Long
Dim NN As Long
Dim IsPrime As Boolean

For Num = 2 To 1000000
IsPrime = True
For NN = 2 To Int(Num / 2)
If Num Mod NN = 0 Then
IsPrime = False
Exit For
End If
Next
If IsPrime Then
MsgBox CStr(Num) + " is a prime number!"
End If
Next
End Sub

Timeline of Visual Basic (VB1 to VB6)

noreply@blogger.com (Kaleng) — Tue, 27 May 2008 05:51:00 +0000

Project 'Thunder' was initiated Visual Basic 1.0 (May 1991)
was released for Windows at the Comdex/Windows World trade show in Atlanta, Georgia.

Visual Basic for MS-DOS Visual Basic 1.0 for DOS was released in September 1992.
The language itself was not quite compatible with Visual Basic for Windows, as it was actually the next version of Microsoft's DOS-based BASIC compilers, QuickBASIC and BASIC Professional Development System. The interface used the "COW" (Character Oriented Windows) interface, using extended ASCII characters to simulate the appearance of a GUI.

Visual Basic 2.0 was released in November 1992.
The programming environment was easier to use, and its speed was improved. Notably, forms became instantiable objects, thus laying the foundational concepts of class modules as were later offered in VB4.

Visual Basic 3.0 was released in the summer of 1993;
and came in Standard and Professional versions. VB3 included version 1.1 of the Microsoft Jet Database Engine that could read and write Jet (or Access) 1.x databases. Visual Basic 4.0 (August 1995) was the first version that could create 32-bit as well as 16-bit Windows programs. It also introduced the ability to write non-GUI classes in Visual Basic. Incompatibilities between different releases of VB4 caused installation and operation problems.

version 5.0 (February 1997),
Microsoft released Visual Basic exclusively for 32-bit versions of Windows. Programmers who preferred to write 16-bit programs were able to import programs written in Visual Basic 4.0 to Visual Basic 5.0, and Visual Basic 5.0 programs can easily be converted with Visual Basic 4.0. Visual Basic 5.0 also introduced the ability to create custom user controls, as well as the ability to compile to native Windows executable code, speeding up calculation-intensive code execution.

Visual Basic 6.0 (Mid 1998)
VB6 has entered Microsoft's "non-supported phase" as of March 2008. Mainstream Support for Microsoft Visual Basic 6.0 ended on March 31, 2005. Extended support ended in March 2008. In response, the Visual Basic user community expressed its grave concern and lobbied users to sign a petition to keep the product alive. Microsoft has so far refused to change their position on the matter. Ironically, around this time, it was exposed that Microsoft's new anti-spyware offering, Microsoft AntiSpyware (part of the GIANT Company Software purchase), was coded in Visual Basic 6.0. Windows Defender Beta 2 was rewritten as C++/CLI code.

Characteristics present in Visual Basic

noreply@blogger.com (Kaleng) — Tue, 27 May 2008 05:50:00 +0000

Visual Basic has the following traits which differ from C-derived languages: Boolean constant True has numeric value −1.[3] This is because the Boolean data type is stored as a 16-bit signed integer. In this construct −1 evaluates to 16 binary 1s (the Boolean value True), and 0 as 16 0s (the Boolean value False). This is apparent when performing a Not operation on a 16 bit signed integer value 0 which will return the integer value −1, in other words True = Not False. This inherent functionality becomes especially useful when performing logical operations on the individual bits of an integer such as And, Or, Xor and Not.[4] This definition of True is also consistent with BASIC since the early 1970s Microsoft BASIC implementation and is also related to the characteristics of microprocessor instructions at the time. Logical and bitwise operators are unified. This is unlike all the C-derived languages (such as Java or Perl), which have separate logical and bitwise operators. This again is a traditional feature of BASIC. Variable array base. Arrays are declared by specifying the upper and lower bounds in a way similar to Pascal and Fortran. It is also possible to use the Option Base statement to set the default lower bound. Use of the Option Base statement can lead to confusion when reading Visual Basic code and is best avoided by always explicitly specifying the lower bound of the array. This lower bound is not limited to 0 or 1, because it can also be set by declaration. In this way, both the lower and upper bounds are programmable. In more subscript-limited languages, the lower bound of the array is not variable. This uncommon trait does exist in Visual Basic .NET but not in VBScript. OPTION BASE was introduced by ANSI, with the standard for ANSI Minimal BASIC in the late 1970s. The extension to using a form of DIM A(1976 TO 2020) was first introduced in BBC Basic, found on the BBC micro, which in turn was influenced by COMAL. Relatively strong integration with the Windows operating system and the Component Object Model. Banker's rounding as the default behavior when converting real numbers to integers with the Round function. Integers are automatically promoted to reals in expressions involving the normal division operator (/) so that division of an odd integer by an even integer produces the intuitively correct result. There is a specific integer divide operator (\) which does truncate. By default, if a variable has not been declared or if no type declaration character is specified, the variable is of type Variant. However this can be changed with Deftype statements such as DefInt, DefBool, DefVar, DefObj, DefStr. There are 12 Deftype statements in total offered by Visual Basic 6.0. The default type may be overridden for a specific declaration by using a special suffix character on the variable name (# for Double, ! for Single, & for Long, % for Integer, $ for String, and @ for Currency) or using the key phrase As (type). VB can also be set in a mode that only explicitly declared variables can be used with the command Option Explicit.

Language features

noreply@blogger.com (Kaleng) — Tue, 27 May 2008 05:47:00 +0000

Language features

Visual Basic was designed to be easy to learn and use. The language not only allows programmers to create simple GUI applications, but can also develop complex applications as well. Programming in VB is a combination of visually arranging components or controls on a form, specifying attributes and actions of those components, and writing additional lines of code for more functionality. Since default attributes and actions are defined for the components, a simple program can be created without the programmer having to write many lines of code. Performance problems were experienced by earlier versions, but with faster computers and native code compilation this has become less of an issue. Although programs can be compiled into native code executables from version 5 onwards, they still require the presence of runtime libraries of approximately 2 MB in size. This runtime is included by default in Windows 2000 and later, but for earlier versions of Windows or Windows Vista, it must be distributed together with the executable. Forms are created using drag and drop techniques. A tool is used to place controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have attributes and event handlers associated with them. Default values are provided when the control is created, but may be changed by the programmer. Many attribute values can be modified during run time based on user actions or changes in the environment, providing a dynamic application. For example, code can be inserted into the form resize event handler to reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text box, the program can automatically translate the case of the text being entered, or even prevent certain characters from being inserted. Visual Basic can create executables (EXE files), ActiveX controls, DLL files, but is primarily used to develop Windows applications and to interface web database systems. Dialog boxes with less functionality (e.g., no maximize/minimize control) can be used to provide pop-up capabilities. Controls provide the basic functionality of the application, while programmers can insert additional logic within the appropriate event handlers. For example, a drop-down combination box will automatically display its list and allow the user to select any element. An event handler is called when an item is selected, which can then execute additional code created by the programmer to perform some action based on which element was selected, such as populating a related list. Alternatively, a Visual Basic component can have no user interface, and instead provide ActiveX objects to other programs via Component Object Model (COM). This allows for server-side processing or an add-in module. The language is garbage collected using reference counting, has a large library of utility objects, and has basic object oriented support. Since the more common components are included in the default project template, the programmer seldom needs to specify additional libraries. Unlike many other programming languages, Visual Basic is generally not case sensitive, although it will transform keywords into a standard case configuration and force the case of variable names to conform to the case of the entry within the symbol table entry. String comparisons are case sensitive by default, but can be made case insensitive if so desired. The Visual Basic compiler is shared with other Visual Studio languages (C, C++), but restrictions in the IDE do not allow the creation of some targets (Windows model DLL's) and threading models.

Visual Basic

noreply@blogger.com (Kaleng) — Tue, 27 May 2008 05:09:00 +0000

Visual Basic
From Wikipedia, the free encyclopedia

This article is about the Visual Basic language shipping with Microsoft Visual Studio 6.0 and earlier.
Visual Basic (VB) is a third-generation event driven programming language and associated development environment (IDE) from Microsoft for its COM programming model.[1] Visual Basic was derived from BASIC and enables the rapid application development (RAD) of graphical user interface (GUI) applications, access to databases using DAO, RDO, or ADO, and creation of ActiveX controls and objects. Scripting languages such as VBA and VBScript are syntactically similar to Visual Basic, but perform differently.[2]
A programmer can put together an application using the components provided with Visual Basic itself. Programs written in Visual Basic can also use the Windows API, but doing so requires external function declarations.
The final release was version 6 in 1998. Microsoft's extended support ended in February 2008 and the designated successor was Visual Basic .NET.

------------------------------------ Bahasa -----------------------------------------

Dari Wikipedia Indonesia, ensiklopedia bebas berbahasa Indonesia.
Langsung ke: navigasi, cari
Microsoft Visual Basic (sering disingkat sebagai VB saja) merupakan sebuah bahasa pemrograman yang bersifat event driven dan menawarkan Integrated Development Environment (IDE) visual untuk membuat program aplikasi berbasis sistem operasi Microsoft Windows dengan menggunakan model pemrograman Common Object Model (COM). Visual Basic merupakan turunan bahasa BASIC dan menawarkan pengembangan aplikasi komputer berbasis grafik dengan cepat, akses ke basis data menggunakan Data Access Objects (DAO), Remote Data Objects (RDO), atau ActiveX Data Object (ADO), serta menawarkan pembuatan kontrol ActiveX dan objek ActiveX. Beberapa bahasa skrip seperti Visual Basic for Applications (VBA) dan Visual Basic Scripting Edition (VBScript), mirip seperti halnya Visual Basic, tetapi cara kerjanya yang berbeda.
Para programmer dapat membangun aplikasi dengan menggunakan komponen-komponen yang disediakan oleh Microsoft Visual Basic Program-program yang ditulis dengan Visual Basic juga dapat menggunakan Windows API, tapi membutuhkan deklarasi fungsi eksternal tambahan.
Dalam pemrograman untuk bisnis, Visual Basic memiliki pangsa pasar yang sangat luas. Dalam sebuah survey yang dilakukan pada tahun 2005, 62% pengembang perangkat lunak dilaporkan menggunakan berbagai bentuk Visual Basic, yang diikuti oleh C++, JavaScript, C#, dan Java.