VS 2010 Beta 2 Read Me Items for Web Deployment

There are some known issues/bugs related to VS 2010 Web Deployment features in VS 2010 Beta 2 Read Me� I can imagine reading the entire Beta 2 read me file can be daunting so I thought I can just copy paste the ones related to Web Deployment here�

DB Deployment will fail if the Database Name is longer than 127 characters

Description: If you are using latest VS 2010 Web Deployment Features and trying to deploy your database using the Deploy SQL property page then at times you might get error from VSMsDeploy task. 

There might be several reasons for the failure including connection and authentication issue but a current bug in the product does not allow you to script schema/data from a database (typically SQL Express MDF file) if the file path is longer than 127 characters.  In the OS like XP or Win2K3 the default path for the VS project & its default ASP.NET Login/Profile DB could be something like C:\Documents and Setting\... \Visual Studio 2010\Projects\MyProject\App_Data\ASPnet_DB.mdf... This path can potentially exceed 127 characters and result into Deployment failure...

Workaround: The easy work around is to have the project copied to a location where the path will not exceed 127 characters for e.g. C:\MyProject\App_Data...  This issue will eventually be resolved in the product...

Some VS 2010 Web Deployment Features will not work if VS 2010 is installed on Vista RTM instead of Vista SP1

Description:  If you are using the new Web Deployment feature set in VS 2010 and are using the below features which integrate with MSDeploy:

• Web Packaging
• One-Click Publishing
• DB Deployment

then you will have to use Vista SP1 instead of Vista RTM as your OS.

Workaround: MsDeploy requires features which are built inside Vista SP1 and hence trying to run Web Deployment features on Vista RTM fails.  This is a required dependency so you will have to use Vista SP1 as your OS for VS 2010.  Do note that you can still use any other operating system like XP, Win2K3, Win2k8 R2, Win7 etc to install VS 2010 and use the Web Deployment features, it is just advised that any of the OS versions that you use are updated with the latest Service Packs so that all the required dependencies are in place.

MsDeploy.exe.config file will be required to run Web Deployment on machines with .NET 4.0 only

Description: If you installed VS 2010 on a clean machine which does not have .NET 2.0 (e.g Win2K3)  and are trying to use the VS 2010 Web Deployment Features then when you run the deploy.cmd file to install your web package you might receive error stating "Msdeploy.exe -.NET Framework Initialization Error Unable to find a version of the runtime to run this application."  This is due to the fact that VS 2010 comes with only .NET 4/CLR4 and and CLR 4 does not allow CLR 2.0 executables to run  without having an explict exe.config file�  If you are using other .NET 2.0/3.0 or 3.5 exes on a box with just .NET 4 then you might face similar issues with those EXEs too�

Workaround: You can easily work around this by going to "%Program Files%\IIS\Microsoft Web Deploy" (& additionally also on "%Program Files (x86)%\IIS\Microsoft Web Deploy" folders and create following msdeploy.exe.config file in there

<configuration>
    <startup useLegacyV2RuntimeActivationPolicy="true">
            <supportedRuntime version="v2.0.50727" />
            <supportedRuntime version="v4.0" />
    </startup>
</configuration>

This issue will be fixed in the future releases of the product.

-Vishal

Migrating from Visual Basic 6 to Visual Basic .Net/2005

Abstract
As a Visual Basic 6.0 programmer, what is the roadmap forward for your applications? As Visual Basic 6.0 becomes �deprecated technology� what will you do with your enterprise class applications written in Visual Basic 6.0. This article is the musings of a developer that has been looking at migrating existing enterprise-class Visual Basic 6.0 applications to Visual Basic 2005.
Introduction
If you have been a serious Visual Basic 6.0 programmer with very sizeable code investments in Visual Basic (we have 22 enterprise level applications), at least 18 of which are written with Microsoft Visual Basic

, crunch time comes when you begin to think or when you decide to advance your applications to new versions. Crunch time comes when all of a sudden, your Visual Basic 6.0 projects don�t open properly anymore in the Visual Basic 6.0 IDE (especially when running on Windows Vista with Visual Studio 2005

installed). Crunch time comes most especially when it dawns on you that you are basically using �deprecated� technology, that between Visual Studio 6.0 (which contained Visual Basic 6.0) and Visual Studio 2008 (the latest version of Microsoft�s Visual Studio development suite), they have been 4 (four) new versions of Visual Basic.
Crunch time is the realization that for your software business to live, you will have to do something about your existing Visual Basic 6.0 applications. Our purpose in writing this article is to share our experiences of what we found as we endeavored to start to upgrade our Visual Basic 6.0 applications, and to discuss some of the touch decisions and choices that will undoubtedly have to be made.
Appraising the current Visual Basic situation!
What made Visual Basic special was its power, elegance and simplicity! It largely retained the style and syntax of the Basic language as we knew it i.e. if you had been using GW Basic, QBasic, Microsoft Basic Professional Development System (we shall call of these �Microsoft�s Basic�), etc, you could look at Visual Basic code and read it and understand it. Changing over from those early flavors of Microsoft�s implementation of the Basic programming language to Visual Basic was thus not difficult. In fact, the skills you learnt from using those early implementations of Basic made it easy and possible to immediately start building Windows database applications on Microsoft Access 2 using then Access Basic as implemented on those versions of Microsoft Access even though you had to learn a few new keywords and perhaps had to deal with the situation that some language features you knew had been removed!
Further evolutions of Microsoft�s Basic implementations ensured that the Basic language as we knew it was preserved and skills of the Visual Basic programmer were further enhanced when Microsoft made Visual Basic the �unified programming/macro environment� for its leading Microsoft Office suite of productivity applications as well as the premier scripting language for its ASP (Active Server Pages) Web development system. Despite the very slight variations between Visual Basic, Visual Basic for Applications (VBA), and VBScript, Microsoft�s Basic was Microsoft�s Basic and it was not difficult for the Visual Basic Programmer or someone with skills in some other implementation of Basic for that matter to be able to switch between any of these three core environments or implementations of Microsoft�s Basic!
Now coming to Visual Basic 6, the most powerful and elegant release of these flavors (prior to the .NET flavors) of Microsoft�s Basic, the Microsoft Solutions Framework (MSF) emphasized a componentized systems design and development approach in which the meat of your application (data access code, data manipulation code and business rules) could all be built as COM (Component Object Model) components hosted on MTS/COM+. Your application front-end (Visual Basic Forms or ASP Web Pages) could then call these components to obtain any services required. The backend could be any database system that had an ODBC Driver or OLE DB provider. The front-end as already noted could of course be Visual Basic Forms (if you wanted your application to run as a Windows application) or ASP (if you wanted your application to run as a Web application).
Your data-aware classes could easily establish connections to the database and then create recordset objects in its Init event that could then be returned to a calling application by calling the GetDataMember method of such a class.
Even in terms of data access technology, if you had been using DAO (Data-Access Objects) or RDO (Remote Data Objects) in versions of Visual Basic prior to version 6, changing over to using ADO (ActiveX Data Objects) was not very difficult since both technologies had similar terminology and interface (e.g. A recordset object in DAO was similar in concept to a Recordset Object in ADO) and methods of processing the objects returned.
This then is a general and short summary of what Basic programmers using Microsoft�s implementation of that language have had to deal with until the arrival of Visual Basic .NET flavors of Basic.
What is all the Hullaballoo about?
Visual Basic programmers expected Microsoft to maintain the look and feel of Microsoft�s Basic that we had always known (especially in the language implementation). But behold! What did Microsoft choose to do?  They decided to fulfill the biblical prophecy recorded at Zephaniah 3:9 which states �For then I shall give the peoples a change to a pure language, in order for them to call upon the name of Jehovah, in order to serve him shoulder to shoulder�.
The attempt to fulfill this biblical prophecy resulted in Microsoft�s attempt to create the New Jerusalem (the .NET Framework) and of course as we now know it, the .NET Framework languages! The result has been a massive genetic modification of the Visual Basic language and an attempted premature extinction of �perceived dianosaurs� (e.g. Visual FoxPro).
If you are a lover of �game meat� and Visual Basic prior to .NET was a charming wild mountain goat (an Ibex on the Highlands of Ethiopia), and you were then given the �new � Visual Basic (i.e. the .NET Flavors of Visual Basic), you would not want to eat the meat at all because the color of the animal has changed, its size has changed (it looks more bloated), its natural smell has changed (it smells not like Basic but like C/C++), even its meat tastes different (not the C/C++ like syntax for writing code)�the grand creator (Microsoft) says it is the same or better but we all (aspiring citizens of the New Jerusalem) can see it is not! You cannot even open a Visual Basic 6.0 project in Visual Basic 2005 and expect it to run�it is that bad!
Crunch Time!
The million dollar question then is �If you are a Visual Basic 6.0 Programmer with significant code investments, what would you do?� Should you migrate to other implementations of the Basic Programming language such as REALbasic 2009 (from Real Software Inc) or Liberty Basic? Should you try Visual Basic 6 lookalikes that also offer multi-platform compatibility such as Jabaco 1.4 (by Manuel Siekmann) or should you just rewrite your code in Visual Basic 2005/.NET? What alternatives did we find and what choices will have to be made?
Jabaco: Jabaco is startlingly like Visual Basic 6.0. Even the startup forms, property windows, toolbox, project explorer are astonishingly like Visual Basic. What is more, even the code syntax you write is pure VB 6-like! We made a copy of our Fixed Assets Software system and then opened it in Jabaco (we are using Windows Vista Home Basic) and the conversion process was seamless. To run the code, we made some minor changes (e.g. Converting Currency to Double) or removing Windows Controls such as the toolbar control and that was that! The structure of the Jabaco code, its keywords, its syntax, the functions and procedures are Visual Basic 6 alike. Even the way you make your Exe�s after writing your program was simple and straight forward. If you are a Visual Basic 6.0 programmer, and you are looking for a secure non-Microsoft way forward for your projects, you will feel instantly at home with Jabaco 1.4 from the very minute you start the application�you can start writing tons of code immediately! When we tried to run our program (both on Windows XP SP2 and Windows Vista Home), we were pleased to see that it could run without hitches! Jabaco would compile your application to Java byte code. In addition, Jabaco is free! The big cat is certainly prowling � power, elegance, speed, simplicity, multi-platform capability by compiling to Java plus a pure preservation of the spirit of Visual Basic�this is Jabaco!
Liberty Basic: Liberty Basic appear to offer a nice RAD look and feel! The method for building your application is reverse to what you normally do with Visual Basic 6 where you would draw your form�s on a Canvas! Liberty Basic is indeed a free-spirit, a true implementation of the Basic Programming Language! We did not test drive this tool! You would definitely have to look at this one for yourself�we have not evaluated this tool closely!
True Basic: True Basic is another viable alternative to Visual Basic! This implementation of the Basic programming language is touted as the true descendant of the original Dartmouth Basic and is available in Silver, Bronze and Gold editions. Again, we could not test drive this tool but product descriptions sure make it look like a powerful alternative to Visual Basic!
REALbasic 2009 R3: What about REALBasic 2009! We had known of this tool for sometime, having come across a white paper that we downloaded on the Internet! We downloaded a 30-day evaluation of the REALbasic 2009 R3 from the product website (www.realsoftware.com)! As with Jabaco, installation was a breeze! If we can consider Visual Basic 6.0 to have been a charming wild mountain goat on the highlands of Ethiopia, you may consider REALbasic as beautiful and dainty wild goat variety such as those found on the forests of Cyprus -  a beautiful and tasty variety indeed! A powerful viable alternative to Visual Basic .NET/2005! A Visual Basic 6.0 programmer could look at REALbasic code and readily enough read it understandably despite some minor differences in code structure! Both languages (Visual Basic 6 and REALbasic 2009) share many keywords and reserved words in common even though! Even though the IDE is different, it is readily enough understandable! Unlike Jabaco, REALbasic will not allow automatic conversion of Visual Basic 6.0 projects (or perhaps we did not look deeply enough) but rewriting your Visual Basic 6.0 code in REALbasic should definitely not be as difficult as doing a rewrite in Microsoft�s own Visual Basic 2005! Another attraction to REALbasic was that it ships with its own Client/Server SQL Database so that you can be up, building database applications quickly! This would mean that if you are using REALbasic, you would be obtaining a complete applications development studio (everything you need in the package)! And then to boot, REALbasic is multi-platform capable, allowing you to compile directly to Machine code (for windows, MAC OS and several other OS�s) thus achieving significant performance gains similar to those of C/C++ flavors that also compile to machine code! We think that the differences between REALbasic and Visual Basic can be accounted for in the motivation behind the creation of the language�the fact that the creators of REALbasic are in this for real�they are offering a genuine, powerful, viable, non-Microsoft alternative to Visual Basic.
Microsoft Visual Basic 2005: And what about Microsoft�s Visual Basic 2005 (this is what we have installed to enable us start conversion of our programs)? We cannot pretend that we are happy with the fact that we are required to re-write major league enterprise applications almost bottom up! As very experienced Visual Basic developers, we had expected to get up and quickly using the new Visual Basic (but that was not to be)!
 Be that as it may, Microsoft�s pioneering efforts in programming language design and innovation cannot be just discounted! The new Visual Basic 2005 is not Visual Basic 6 but it does stand shoulder-to-shoulder with C# (Microsoft�s new toy), J# and Visual C++ in terms of syntax and programming constructs! The New Visual Basic 2005 also includes expanded project types and language capabilities! It also has enhanced language constructs and new data types that will easily put you at par with the C# or C++ programmer while providing tools to rapidly create Web applications and access the latest versions of Microsoft�s own SQL Server 2008 and Oracle 10g/11g.
If it is name recognition that you want (Microsoft is a known name world-wide and their marketing power is unmatched); if you want to be a developer building applications with tools from an �approved supplier� then you will have to embrace the new Visual Basic 2005 (Visual Basic 2008 has already been released as at the time of writing)�learn to eat genetically modified meats with a slightly different taste and feel so that you do not starve to death!
I think it is worth mentioning if you must stick with Microsoft that C#, Microsoft�s new C-like language that Microsoft created specifically for .NET Framework programming can also be a powerful contender! We found that mastering C# was both exciting and fun, probably because I was aware that I was learning a completely new programming language and therefore had no preconceptions of what to expect! On the contrary, learning Visual Basic 2005 was not so much fun perhaps because I approached the language as a Visual Basic programming veteran! I expected the language and keywords to be familiar enough! I expected the program structure to be familiar! I expected programming constructs and abstractions to be familiar! If you are a Visual Basic 6.0 programmer hoping to mater Visual Basic 2005 quickly, be forewarned � simply disabuse your mind! Approach Visual Basic 2005 as if you knew nothing at all about Visual Basic, approach it as if you are learning a completely new language that you have never really used for large-scale commercial projects (like say C/C++)and you will master Visual Basic 2005 soon enough!
Conclusion
All the options I have examined will involve some amount of code re-write! They can be no avoiding that no matter how little and I guess that is the risk attendant to our trade is it not?  If you want to keep your VB6 code almost as pure as it is, Jabaco is it! Otherwise, REALbasic is the next best alternative! If you want to stick with Microsoft, you would have no choice but to go Visual Basic 2005 because alas! Microsoft�s massive marketing machine ensures that most companies requesting new software (especially for those of us in the bespoke) software market are all requesting their projects in Visual Studio .NET! Also, it is a reality that the next generation of programmers being trained are being trained in Microsoft�s Visual Studio .NET as exemplified by the new popularity of C#
And what about us? We are taking a serious look at Visual Basic 2005, learning to like and desire the new meat so to speak! But we plan to also be delivering cross-platform solutions in Jabaco! Our quest for a solution brought us in touch with great tools out there being built by little known companies�it is worth checking out!

Source Code VB 6.0 untuk Sistem STOK Sederhana dengan MySQL

Dibawah akan saya berikan link source code sistem Stok Sederhana dengan menggunakan database MySQL dan Crystal Report 8.5. Sebelumnya mohon maaf apabila ternyata kurang berkenan, karena source code ini adalah bagian tugas kuliah saya beberapa tahun yang lalu.

Isinya perpaduan antara Adodc dan ADODB, serta sebagian menggunakan Syntax SQL. Semuanya dapat Anda unduh dengan cuma-cuma. Bagi yang belum pernah menggunakan database MySQL, sebaiknya membaca 3 tulisan saya sebelumnya, mengenai instalasi Xampp, driver MySQL, Data Source Name, dan koneksi MySQL dengan Visual Basic 6.0

Petunjuk Penggunaan Source Code :

1. Unduh filenya pada link di bagian bawah tulisan ini
2. Exctract semua file ke dalam sebuah folder
3. Sudah harus terinstall Xampp dan software sejenis misalnya PHPtriad, dll.
4. Copy Folder inventory ke C:\xampp\mysql\data\ (mengikuti dimana Xampp anda install, intinya pada folder mysql\data\
5. Buat data Source Name dengan nama "myodbc", keneksikan dengan database inventory.
6. Untuk reportnya Anda perlu membukanya satu persatu dan dikoneksikan ulang dengan set location dan koneksikan dengan "myodbc"

Link Download Source Code Sistem Stok Sederhana dengan MySQL

http://freeaudit.co.cc/index.php/download12/50-source-code-mysql, untuk dapat mengaksesnya sebelumnya harus register dulu ya! terima kasih semoga bermanfaat

Visual Basic .net Programming

Visual Basic.NET is a robust, versatile programming language designed for Web Based as well as Windows based application development. The language has been used by programmers to develop professional applications and offers advantage of the features of .NET environment. Visual Basic .net programming offers a variety of object oriented features that were previously available with Java, C++ only.

The applications that are used in a business environment involve the manipulation of the data that are part of relational databases. Visual Basic.net programming is an object oriented language that is an evolutionary version of Visual Basic, which is implemented on .NET framework. Most of the VB.NET developers use Visual Studio .NET as their IDE, integrated development environment.
Many changes have been incorporated in Visual Basic .NET to make it easier to use and more powerful than Visual Basic 6.0. It has an interesting and useful feature of garbage collection that is administered by a Common Language Runtime and helps to provide better memory management. As the system is universal it offers greater interoperability besides contributing in enhancing the power and flexibility available in Visual Basic .net programming.
Paladin Consultants offers custom software development in a number of languages that include C, C++, Visual Basic, .Net technology, Java, SQL Server, JavaScript, and Visual Basic .net programming etc. We have developed a variety of software that are used in wide range of businesses such as Robotics, CRM applications, Accounting, Industrial along with a number of Financial engineering programs that are used by various corporations.
Paladin Consultants offers customized solutions as per the business type and its specific requirements. After a deep and carefully study of the websites, software solutions are designed by incorporating Rapid Application Development (RAD) methodology. RAD involves use of object oriented or functional modular routines in the project. The modular nature of the routine offers three advantages that include re-useable code, identification of logical objects in the business model along with swapping of the objects. All these advantages help the model to be more responsive for future usage.
Paladin offers a vast variety of services besides offering custom software development that include database design, IT consulting, website design and Visual Basic .net programming services. We are located in metropolitan New York and offer software development to business organizations. Visit the site www.paladn.com and know more about the services offered by the .net Programming Consultants New Jersey Company.

Visual Basic Programming Language and Its Significant Features

Visual Basic

is a third generation event-driven programming language

. The Microsoft Corporation released Visual Basic in 1987. It was indeed the first visual development tool from Microsoft. Visual Basic was derived from BASIC and enables rapid application development of graphical user interface applications, access to databases using DAO, RDO, or ADO, and creation of ActiveX controls and objects. The language not only allows Visual Basic programmers to create simple GUI applications, but also helps them develop quite complex applications. Visual Basic allows developers to target Windows, Web, and mobile devices.

Programming in Visual Basic is a combination of visually arranging components on a form, specifying attributes and actions of those components. Since the default attributes and actions ought to be defined for the components, it is very simple to write a program without the help of a Visual Basic programmer. Forms can be created using drag and drop techniques. Visual Basic provides many interesting sets of tools to help you in building exciting and entertaining applications. It provides these tools to make your life easier, since the entire coding is already written for you. Moreover, it is a user friendly language which is very effective and efficient. A tool is used to place controls such as text boxes, buttons, etc on the form window. Default values will be provided when a control is created, but it can be changed by the Visual Basic programmer.

Visual Basic is not only a programming language, but it also has a complete graphical development environment. Visual Basic has the ability to develop programs that can be used as a front end application to a database system, and serving as the user interface which collects input from the user and displays formatted output in an attractive format. As the Visual Basic programmer works in the graphical environment, much of the program code is automatically generated by the Visual Basic program. The main object in Visual Basic is called a form. Once you create forms, you can change the properties using properties window. Finally, you can add events to your controls. Events are responses to actions performed on controls.

Using Visual Basic's tools, you can quickly translate an abstract idea into a program design which you can actually see on the screen. VB encourages you to experiment, revise, correct, and network your design until the project meets your requirements. Visual Basic Programmer use the language in different areas such as Education, Business, Accounting, Marketing and Sales. Visual Basic supports a number of common programming constructs and language elements. Once you understand the basics of the language, you can create powerful applications using Visual Basic.

Visual Basic can create executables i.e. EXE files, ActiveX controls, but it is primarily used to develop Windows applications. It is also used to interface web database systems. This generation of Visual Basic continues the tradition of giving you a faster and easier way to create .NET framework-based applications. Visual Basic also fully integrates the .NET framework and the common language runtime, which provide language interoperability, garbage collection, enhanced security, and versioning support.

Querying Table Data Using Visual Basic Code in Ms Access

In order to fully utilize the capabilities of MS Access

, one must learn not only learn the Visual Basic

(VB) programming language, but should also learn Standard Query Language (SQL). Once a grasp of these two languages have been obtained, MS Access users can begin to build faster and more efficient databases.

One tool that has proved itself very useful to me over the years is querying data from tables or queries using VB and SQL code. A brief introduction to this process is presented in this article. To best understand this process, an example is provided below along with an explanation of its parts.

�*********CODE***********
Dim rstTemp As Recordset
Dim strSQL As String
Dim routeNum As Integer

strSQL = "SELECT [Route], [Main Route PM], [Intersecting Route], [IntBeginPM], [IntEndPM] �
strSQL =  strSQL + �FROM Intersections_list WHERE (((CStr([Route])) = """ + cmbRouteQuery + """));"

Set rstTemp = CurrentDb.OpenRecordset(strSQL, dbOpenDynaset)

If (Not (rstTemp.EOF)) Then
    rstTemp.MoveFirst
    routeNum = rstTemp(0)
�************************
After the initial variable declarations, the code assigns an SQL statement to the string variable strSQL. This statement directs Access to gather all the data in the Route, Main Route PM, Intersecting Route, IntBeginPM, and IntEndPM fields of the table named Intersections_list. Furthermore, it directs Access to only gather information from these fields where the Route field is equal to a value held in the combo box cmbRouteQuery.

Once the SQL statement has been set, it is passed to the next line of code which executes it. It should be noted that the dbOpenDynaset variable is built into Access and holds an integer value that changes the type of recordset to open. For most general purposes, using dbOpenDynaset will work just fine.

The �if statement� in the code example

verifies that the recordset just created contains information. If information is present, the code directs Access to move to the first record in the recordset. The code then stores the route in the first record (routeNum = rstTemp(0)) in the variable routeNum to be used for later use.

Open Source Vs. Closed Source Software: The Great Debate

Open source software can be defined as software distributed under a licensing agreement which allows the source code (computer code) to be shared, viewed and modified by other users and organisations.


Cost

Open source software is free. This is a huge draw card, and if your in-house capabilities are such that you are able to implement, train and support at little cost to your organization it may be an attractive option. Having said that, open source software requires a certain level of technical expertise in order to manage content. It is therefore important to take into consideration the costs incurred once the software is obtained may be substantial unless the resources are already in place to manage it. Long term costs include the cost of implementation, innovation, the opportunity cost incurred battling with service/support issues, and the costs associated with investment in infrastructure due to a general inability to scale (assuming the organisation will grow and develop and will therefore have evolving requirements). Notably, open source software providers are increasingly charging for add- ons, additional services and integration. The total cost of ownership for open source software may roughly equal some closed source options as a result.

Service and Support
Service is one of the key issues regarding open source software. Open source software relies on its online community network to deliver support via forums and blogs. While there are massive, loyal and engaged online communities that users can turn to, time-poor consumers of today are familiar with the immediate service and support that enables issues to be resolved in a timely manner, and these communities cannot guarantee the high level of responsive service and support proprietary software can offer.

Innovation

Open source software enables innovation by providing users with the freedom and flexibility to adapt the software to suit, without restriction. However, innovation may or may not be passed on to all users of the
software. It is a user�s prerogative whether they wish to share their innovation with any online communities, and users must be actively participating in these communities to become aware of such innovations. It has been debated whether customized changes to the original source code limit the future support and growth of the software, as these can potentially result in a limited ability to apply future updates, fixes or modules aimed at improving the software, leaving the user with a version that may have irresolvable issues. It is relevant to note that open source software providers generally struggle to attract large scale R&D.

Usability

Open source software has been highly criticized for its lack of usability, as generally, the technology is not reviewed by usability experts and does not cater to the vast majority of computer users. Open source software is generally developer-centric, and without system administration experience or the knowledge required to manipulate programming language, use of the software and ability to fix errors as they arise is often limited to those with technical expertise. Furthermore, open source software does not legally require documentation such as user manuals or guides, hindering the creation of such tools. When
documentation is provided, it is often general, containing implicit jargon, inhibiting learning. Without adequate documentation users must rely on alternative means such as online communities, assuming they are capable of finding them and the problem is one others have encountered or are willing to help resolve.

Security

Open source software is often viewed as having security issues. New data from Forrester Research has shown that 58% of IT Executives and technology decision makers in large companies are concerned about the security of open source software. Open source software is not necessarily developed in a controlled environment. While big players often have a concentrated development team, oftentimes the software is being developed by individuals all over the world who may not work on the software for the duration of its developing lifetime. This lack of continuity and common direction can lead to barriers to effective communication surrounding the software. Furthermore, open source software is not always peer reviewed or validated for use. While users are free to examine and verify source code, the level of expertise required means that it is entirely possible for a programmer to embed back door Trojans to capture private and confidential information without the user ever knowing. Adopting a reputable brand with a concentrated development team supported by a strong online community will reduce the potential risk.

2) Closed Source Software

Closed source software can be defined as proprietary software distributed under a licensing agreement to authorized users with private modification, copying and republishing restrictions.

Cost

The cost of proprietary software will vary from a few thousand to a few hundred thousand dollars, depending on the complexity of the system required. This cost is made up of a base fee for software, integration and services and annual licensing support fees. This cost may be prohibitive for some; however what the user is paying for is a more customized product from a trusted brand that includes higher levels of security and functionality, continuous innovation, a greater ability to scale, ongoing training and support and a lower requirement for technical skills. In order to support these elements and maintain high availability websites, a mechanism must be in place to recoup the costs. As mentioned previously, increasingly open source software providers are also charging for add-ons, additional services, and integration, reducing the gap in cost between the two options.

Service and Support

If the internet is an important channel for an organisation, software is often a secondary concern, with service level and support structure requirements taking precedent in favour of maximising uptime and minimising downtime. Service is probably the greatest advantage of using proprietary software. Proprietary software providers offer ongoing support to users, a key selling point for users without technical expertise. If the user manual or guide is not enough, or if a user experiences a problem with the software, there is an immediate point of call to turn to for assistance. There is a certain reduction in the risk undertaken with proprietary software because users are working with companies that are viable, and people with intimate knowledge of the products and services being used should any questions arise. Because service is one of the main reasons users choose proprietary over open source software, many proprietary software providers compete on service, increasing the bargaining power of buyers and thereby increasing customer service levels among providers.

Innovation

Proprietary software providers do not allow users to view or alter the source code. While this may be viewed as a disadvantage to some, it ensures the security and reliability of the software. Furthermore, many proprietary software providers customize software for specific users to provide more flexibility while investing in R&D in order to regularly offer new products and upgrades. Moreover, proprietary software providers have online user communities that create value by sharing ideas, strategies and best practices through feedback mechanisms such as forums and surveys, which also foster innovation and allow the product to adapt with changing needs. This innovation comes fully tested, and is available to all users of the software. It does not require investment in R&D or the technical understanding of source code, and assistance with implementation is generally part of the package. Because vendors must ensure their software does not become redundant, users also benefit from the type of targeted innovation undertaken- continuous investment in R&D rather than �innovation for innovation�s sake�, business focused rather than technology focused.

Usability

Proprietary software generally employs expert usability testing, and as the software is normally aimed at a more targeted audience, and therefore more tailored, usability is generally ranked quite high. In addition, detailed user manuals and guides are provided. This enables faster training and provides an immediate reference, allowing users to move along the learning curve more quickly. Supporting services include seminars, targeted training courses and extensive support to help maximise use of the software. It is also important to note that while many people see proprietary software as �closed�, today�s proprietary software offers a vast array of mechanisms for enhancement by third party systems and developers.

Security

Proprietary software is viewed as more secure because it is developed in a controlled environment by a concentrated team with a common direction. Moreover, the source code may be viewed and edited by this team alone, and is heavily audited, eliminating the risk of back door Trojans and reducing the risk of any bugs or issues with the software. For Moreinfo

By: Jefferson Daniel

Koneksi Database MySQL dengan VB 6.0 (3)

Sekarang kita mulai masuk ke visual basic untuk koneksi dengan database MySQL, sebelumnya kita sudah install server lokal dan membuat database sederhana kemudian install odbc driver untuk MySQL nya dan membuat Data Source Name.

Untuk percobaan pertama akan dipakai Adodc sebagai alat bantu koneksi. Oleh karenanya kita tambahkan sebuah Adodc ke dalam form baru. Apabila belum ada komponen Adodc-nya tambahkan dulu dengan cara (klik pada menu bar Project >> component ..., setelah muncul jendela component, cari dan contreng Microsoft ADO Data Control 6.0 (OLE DB) akhiri dengan tombol OK.

Jika sudah ditambahkan ke dalam Form, klik kanan Adodc nya dan atur propertiesnya sebagai berikut :

Pada Jendela Property page - Tab General pilih option Use ODBC Data Source Name, nah DSN yang dibuat sebelumnya akan kita gunakan disini, apabila pembuatan DSN berhasil akan tampak pada daftar drop down dibawah, kemudian pilih yang sesuai (seperti yang dibuat sebelumnya, misal : "myodbc"), klik Apply.

 

Kemudian menuju ke tab Record Source, Command Type pilih "adCmdTable", dan pada Table or Procedure Name pilih nama tabel, misalnya : "Tbarang", akhiri dengan klik tombol OK

Sampai disini koneksi sudah selesai, jika tidak ada komentar (message) yang gak jelas berarti sudah konek. Sekarang kita buktikan apakah sudah benar-benar connect dengan mencoba menampilkan data ke dalam datagrid. Tambahkan sebuah DataGrid (Microsoft DataGrid Control 6.0 (OLE DB)), atur propertiesnya, pada datasource pilih Adodc1. kemudian Run(F5) , bagaimana sudah muncul? semoga ... ^_^.

Bila Anda tidak suka pengaturan properties Adodc yang berbelit-belit seperti diatas Anda dapat copy-paste code dibawah ini sebagai kode koneksinya :


'-----------------------------------------------
Private Sub Form_Load()

Adodc1.ConnectionString = "" &  _

"Provider=MSDASQL.1;Persist Security Info=False;Data Source=myodbc"
Adodc1.RecordSource = "tbarang"
Adodc1.Refresh
DataGrid1.Refresh

End Sub

'-----------------------------------------------


Mudah kan???, untuk tulisan saya selanjutnya akan saya sampaikan syntax-syntax untuk simpan, edit dan hapus yang cocok untuk database MySQL.

Koneksi Database MySQL dengan VB 6.0 (2)

Melanjutkan tulisan saya sebelumnya, saya akan memulai bagaimana koneksi database MySQL yang telah dibuat dengan Visual Basic 6.0, tentunya agar dapat digunakan untuk membangun aplikasi yang lebih user friendly.

Sebelumnya kita memerlukan driver untuk koneksinya, yaitu mysql-connector-odbc-3.51.27-win32, atau dengan versi-versi yang lain. Tanpa driver ini database MySQL tidak akan bisa dikoneksikan dengan visual basic 6.0 maupun program/aplikasi lain. Anda dapat unduh filenya gratis disini. kemudian install file executablenya sampai selesai.

Membuat DSN (Data Source Name)

Tidak seperti koneksi VB 6 dengan microsoft Access yang dapat langsung mengakses file tertentu, untuk koneksi ke database MySQL diperlukan DSN, dimana langkah-langkah membuatnya adalah sebagai berikut :

1. Klik Start Menu >> Control Panel 
   
2. Double Klik Administrative Tools 
3. Double Klik Data Sources (ODBC), sehingga muncul jendela ODBC Data Source Administrator
4. Pada tab user DSN atau System DSN, klik Add ... , sehingga muncul jendela create new data source
5. Cari di List "MySQL 3.51 ODBC Driver", pilih kemudian klik Finish
   
6. Kemudian muncul jendela connector/ODBC 3.51.xx - Add Data Source
   
7. Pada tab login, isikan isian-isian sebagai berikut :
   
   
   

• Data Source Name, isi dengan nama bebas (-yang mudah diingat-), misalnya : "myodbc"
• Description, boleh tidak diisi
• Server, isi dengan "localhost"
• user, isi dengan root untuk yang belum membuat user di database MySQl-nya
• Password, diisi jika user menggunakan password
• Database, pilih database dari list yang ada, misalnya : "inventory"
  
• Jika diperlukan klik tombol Test
• Akhiri dengan tombol OK

Jika pembuatan DSN berhasil akan muncul didaftar User DSN/System DSN, dengan nama sesuai dengan Data Source Name yang dibuat sebelumnya (-misal : "myodbc"-).

Sampai disini pembuatan DSN telah selesai dan siap untuk dikoneksikan dengan Visual Basic 6.0, Tetapi maaf untuk pengaturan koneksi dengan visual basicnya (coding, component yang diperlukan) akan saya sajikan di tulisan saya selanjutnya.

Love Award

 I got this award from All about healty. It's my first award really, thank you so much for this.To accept this award, here are the rules: Post it on your blog together with the name of the person who has granted the award, and his or her blog link. Pass the award to 15 other blogs that you�ve newly discovered. Remember to contact the bloggers to let them know they have been chosen for this award.Now, as for my newly-discovered blogs whose owners are in every way lovelier than I am, I am passing this on to:
 

Islamkucintaku
Kamulagikamulagi
Udahdewasa
Lemariebook
vbopensource
Miawruu
Rumah Blogger
Ana Cristina
HW
Celebrities
Rizky2009182
Awi
Galeri-info
Harun Ismail
Cari ide



                                        

Koneksi Database MySQL dengan VB 6.0 (1)

Dalam pembahasan kali ini akan saya deskripsikan secara ringkas mengenai :

- Instalasi server/host database mySQL

- Cara mengakses database mySQL

- Koneksi database MySQL dengan VB 6.0 menggunakan ODBC

MySQL lazim digunakan sebagai database standar pada hosting (on-line), untuk keperluan pembuatan website dalam hal penyimpanan database. MySQL dapat pula digunakan pada jaringan offline ataupun komputer yang stand alone, untuk dapat mengaksesnya dibutuhkan server lokal, sehingga diperlukan instalasi server lokal terlebih dahulu, misalnya dengan menggunakan software xampp, phptriad, dll.

Instalasi Xampp

link download xampp : http://www.apachefriends.org/en/xampp-windows.html#641

Proses instalasinya cukup mudah tinggal double clik file instalasinya, kemudian next, next dan next sampai finish he3�

Langkah selanjutnya Run Xampp control panelnya, contreng dan tekan tombol start disebelah kanan untuk pilihan Apache dan MySQL nya. Sampai disini instalasi server lokal sudah selesai.

Untuk mengakses database MySQL, syaratnya adalah apache pada control panel diatas telah diaktifkan. Buka browser kita, boleh IE, Firefox atau Opera dll. Kemudian akses alamat ini : http://localhost/phpmyadmin

Membuat database
Cukup ketik sebuah nama database yang kita inginkan misalnya �inventory� pada kotak create new database

Membuat Tabel
Apabila pembuatan database telah berhasil, langkah selanjutnya adalah membuat table, pada kotak Create new table on database inventory, isikan name dan number of field nya. Kemudian tekan tombol �Go�

Tulis/set nama field, tipe, ukuran dll. Setelah selesai klik tombol �save�.

Langkah seperti diatas dapat diulang untuk pembuatan tabel-tabel lainnya. Sampai disini database kita sudah siap untuk diakses dengan Visual Basic 6.0

Untuk bagaimana cara koneksi MySQL ke visual basic 6.0 akan saya sajikan pada posting selanjutnya.

Standart Kode Penamaan Control Pada VB 6.0

Penamaan control sangatlah penting dalam penulisan coding di Visual Basic 6.0, hal tersebut ikut andil dalam efektifitas dan efisiensi kerja seorang programmer ataupun yang masih dalam taraf pemula.Nah, untuk itu dari berbagai sumber buku dan referensi yang lain saya menemukan standar penulisan untuk setiap kontrol pada VB 6

Umumnya penamaan kode diawali dengan 3 karakter di awal penulisan baru kemudian diikuti nama sesuai selera tanpa spasi atau karakter khusus, kecuali tanda _ (contoh : TxtJumlah atau Txt_Jumlah).Standar Penulisan untuk beberapa control dapat dilihat pada daftar di bawah ini :

- Combo box : Cbo
- Check Box : Chk
- Command Button : Cmd
- Directory List Box : Dir
- Drive List Box : Drv
- File list Box : Fil
- Frame : Fra
- Form : Frm
- Grid : Grd
- Horizontal Scrool Bar : Hsb
- Image : Img
- Label : Lbl
- Line : Lin
- List Box : lst
- Menu : Mnu
- Module : Mod
- OLE : Ole
- Option Button : Opt
- Picture Box : Pic
- Resource : Res
- Shape : Shp
- Timer : Tmr
- Vertical Scroll Bar : Vsb 
- Text Box : Txt 

dll.

Walaupun penulisan  kita tidak harus seperti daftar di atas, paling tidak kita dapat gambaran betapa pentingnya penamaan Control yang baik, agar mempermudah dalam penamaan dan nantinya lebih efisien dalam penulisan codingnya. 

Demikian, Semoga  bermanfaat.

Mai Papa ban gaya

Today I am not posting any technical solution or technical information on my techblog but I giving information to all of my blog reader that I am blessed with baby girl. I will write more about it but some other time presently only this information and photos of her.

I am blessed with baby daughter today 12.30PM IST.

Deedi(my elder sister) ordered me to stay at home so she can go and see my daughter, it was feeling like impossible for me to wait but had no option so started writing.

Till yesterday I was too tired, nervous, tensed, confused but today I am flying highest in sky. When I heard crying voice of her I felt a tremendous joy, when I took her in my arms I felt like most hapy person in world. It was greatest feeling I ever had in my entire life. All the exertion of last several months is gone; I do not have word to explain this but what I can do is I can share photos of my sweetheart.

VIDEO TUTORIAL (DEPLOYING USING MERGE MODULES)

Deployment bisa dikatakan sebagai hasil akhir dalam pembuatan aplikasi. Trus bagaimana jadi nya kalau hasil akhir ini tidak bisa di gunakan. Wah pasti sangat menyebalkan. Hal ini bisa terjadi pada aplikasi yang menggunakan Crystal Report. Jika pada saat melakukan deployment tidak menggunakan Merge Modules. Banyak sekali pertanyaan yang masuk ke saya berkenaan dengan ini. �Pak kok setelah di buat installer, trus di install ke PC lain, pas mau lihat laporan kok error�..

�Pak, apa artinya Invalid or Missing KeyCodeV3.dll�. dan banyak lagi.

Jadi untuk menjawab itu semua akan saya buat kan Video Tutorial bagaimana melakukan Deployment suatu project dengan menggunakan Merge Modules.

Silahkan download video tutorial nya disini

Note : untuk video ini saya menggunakan VS.Net 2003

Selamat mencoba ..

Wassalam

Memilih Printer untuk mencetak Report dengan Crystal Report Control (2)

Pada tulisan sebelumnya saya telah menyampaikan bagaimana menampilkan kotak dialog printer sebelum mencetak report ke printer tujuan. Untuk tulisan kali ini agak sedikit berbeda untuk cara mencetak report-nya, yaitu dengan menampilkannya dulu (print preview-) sebelum di cetak ke printer tujuan.

Untuk dapat memilih printer yang mana yang akan digunakan untuk mencetak report, diperlukan beberapa baris code untuk memunculkan button setup printer pada toolbar print preview report. Code-code tersebut adalah sebagai berikut :

Private Sub Command2_Click()
On Error Resume Next
Crt1.Reset
Crt1.Destination = crptToWindow
Crt1.ReportFileName = "C:\Data\Report.rpt"

'SelectionFormula
Crt1.WindowState = crptMaximized
Crt1.WindowShowPrintBtn = True
Crt1.WindowShowPrintSetupBtn = True
Crt1.WindowShowRefreshBtn = True
Crt1.RetrieveDataFiles
Crt1.Action = 1
End Sub

Sebelumnya Tambahkan kedalam Form, sebuah command, sebuah label, dan sebuah Crystal Report Control. Berikan nama Crystal Report Control dengan Crt1 Kemudian Copy-Paste Code diatas di jendela coding.

Kemudian Run program (F5), sehingga akan muncul print Preview report, pada toolbar akan terdapat beberapa button diantaranya button print (untuk langsung mencetak ke printer default), setup printer (untuk memilih printer yang digunakan untuk mencetak), Refresh button, zoom list dan sebagainya.

Untuk memilih terlebih dahulu printer sebelum mencetak, tekan button setup printer, sehingga akan muncul kotak dialog printer sebagai berikut :

Lebih mudah kan? selamat mencoba!!!

Memilih Printer untuk mencetak Report dengan Crystal Report Control (1)

Secara default Crystal Report akan "menganggap" printer yang di "set as default printer" menjadi tujuannya. Bukanlah suatu masalah jika printer yang digunakan mencetak Report hanya satu dengan tipe kertas/kebutuhan yang sama.

Tetapi akan jadi suatu masalah apabila Report yang dihasilkan ternyata membutuhkan beberapa macam printer untuk mencetak report yang memang berbeda jenisnya, misalnya untuk mencetak Slip Gaji diperlukan Printer berjenis pita dan mencetak laporan bulanan menggunakan printer yang berbeda. Akan menjadi pekerjaan yang amat membosankan apabila harus bolak-balik set printer di control panel.

Nah... saya akan berbagi code sederhana dalam Visual Basic 6.0  (-hasil pengalaman pribadi saya-) agar dapat memilih printer tujuan untuk mencetak report saat aplikasi dijalankan.

Kali ini saya menggunakan component Crystal Report Control untuk mencetak Reportnya. Tambahkan kedalam Form, sebuah command, sebuah label, dan sebuah Crystal Report Control. Berikan nama Crystal Report Control dengan Crt1 Kemudian Copy-Paste Code dibawah ini :

Private Sub Command1_Click()
On Error Resume Next
Crt1.Reset
Crt1.ReportFileName = "C:\Data\Report.rpt"
'SelectionFormula

Crt1.RetrieveDataFiles

Crt1.Destination = crptToPrinter
Label1.Caption = ""

Crt1.PrinterSelect
Label1.Caption = Crt1.PrinterName

If   Not Label1.Caption = "" Then
    Crt1.Action = 1
Else
    Exit Sub
End If
End sub



Run Program (F5), kemudian klik command1, sehingga akan muncul Form Dialog Printer,

Nah, sekarang tinggal memilih printer yang mana untuk mencetak report kita, sederhana bukan? Selamat mencoba. Bila ada yang punya jalan lain mohon untuk bisa Sharing disini, terima kasih.