Software Dealer

Software pengisian pulsa elektrik dari SD ke Reseller.

1. Modul Import daftar reseller dr excel.

2. Modul Import Transaksi dari excel.

3. Modul Penjualan disertai print Struk.

3. Modul bisa dipakai untuk gabungan antara barang fisik dan non fisik.

4. Laporan/rekap transaksi.

Software pengisian pulsa elektrik untuk dealer pulsa elektrik

Software pengisian pulsa elektrik untuk dealer pulsa elektrik dengan modul yg lengkap dan pengisian pulsa yg cepat. Sudah di pake oleh puluhan dealer pulsa dengan jumlah transaksi lebih dari 6000 sehari.

Dengan dukungan layanan penuh dijamin aplikasi anda on 24 jam dengan tanpa downtime jika terjadi crash pada server anda system ini dapat pindah ke server lain dengan kondisi sama persis sebelum server anda crash dalam 5 menit.

Modul Software Pulsa ini : Center YM, Center Host to Host, SMS Center GSM 20 terminal, SMS Sender GSM 50 Terminal, SMS Center CDMA 5 terminal, SMS Sender CDMA Terminal 5 , Pengisian pulsa lewat SMS GSM 5 Terminal, Pengisian pulsa lewat SMS CDMA 5 Terminal, USSD GSM MKIOS 20 Terminal, USSD GSM DOMPET XL 5 Terminal, PC Online Telkomsel 5 Terminal, Mtronik 5 Terminal, Three 5 Terminal, Dompet Esia 5 Terminal, SMS Fisik,SMS Complain,SMS Cek Transaksi, Host to Host ke berbagai tujuan spt Eratel, ArtaJasa, Telesindo, Trikomsel, Arjuna, WinPulsa, Simpatindo, DataCell, Aldira, Inova, Boyzone Reload,MultiChip StarMedia dll.

Server engine

Software pulsa sudah terpakai ratusan dealer di seluruh Indonesia.

Asrofi Bagus B

(087870029022).

b_ag_oes@yahoo.com

Seting modem untuk akses internet via gprs kartu gsm im3

Seting modem untuk akses internet via gprs kartu gsm im3 bisa dibilang gampang2 susah, gampang bagi yang udah pernah dan bisa, susah bagi yang belum pernah. Tapi jangan kuatir sebenarnya sangat mudah kok, sekalipun belum pernah seting modem dialup handphone. Akses internet melalui gprs kartu im3 bisa dilakukan langsung melalui handphone maupun melalui komputer, mutlak diperlukan fasilitas gprs yang harus aktif di kartu anda. Bila belum aktif, aktifkan dulu gprs anda, baru baca artikel ini. Biasanya begitu kita aktifkan kartu perdana im3 -setelah proses registrasi- gprs otomatis aktif, kalo belum silahkan telpon 300.

Asumsi gprs di kartu anda sudah aktif, untuk menjadikan handphone sebagai modem dialup langkah2 nya sebagai berikut :

1. Hubungkan handphone anda dengan komputer.

Hubungan handphone dan komputer dapat dilakukan melalui kabel data, infrared, dan bluetooth. Masing2 bisa saling menggantikan, misalnya kalo handphone anda tidak ada kabel data ya bisa pake bluetooth atau infrared, demikian sebaliknya. Dalam artikel ini saya menghubungkan handphone nokia 9300 dengan laptop.

2. Install PC Suite,

Install software PC Suite di laptop atau komputer yang hendak dihubungkan dengan handphone. Bila tidak punya software tersebut bisa download di www.nokia.com , cari apakah handphone anda support PC Suite. PC Suite mensupport beragam jenis koneksi. Kabel, bluetooth, infrared dll.

3. Mengecek Modem (apakah sudah terinstal).

Langkah selanjutnya
setting modem dialup.
Jika PC Suite sudah terinstal dan
handphone anda sudah terdeteksi dengan baik oleh PC Suite berarti modem dapat kita setting, cara mengecek apakah handphone sudah terdekteksi adalah melalui, my computer – properties – hardware – device manager, cek dibagian modems apakah sudah ada Nokia 9300 usb modem. Cek apakah modem bekerja dengan baik dengan cara, klik kanan Nokia 9300 usb modem – properties – dibagian diagnostics tekan tombol query modem, diagnostic akan berlangsung beberapa saat, hasilnya kita bisa lihat di kolom. Jika modem belum terdeteksi coba cek kabel, coba install software PC Suite nya lagi.

4. Setting nomor dial, user name dan password.Untuk dapat men-dial ke internet kita harus mengatur nomor dial, user dan passwordnya. Untuk kartu im3 nomor dialnya adalah
*99***1#, usernya gprs dan passwordnya: im3. Untuk mensettingnya, klik tombol start – all programs – accessories -

communications – new connection wizards – next – pilih connect to internet – next – pilih set up my connection manually – next – pilih connect using a dialup modem – next – pilih nokia 9300 usb modem – next – masukk isp name (dapat diisi apa aja) – next – masukkan nomor dialnya – next – masukkan user name dan paswordnya – next – centang add a shortcut to this connection to my desktop (bila ingin membuat shortcut di desktop) – finish. Setting selesai. Coba klik dua kali shortcut dialup di desktop tadi.

Proses dial berjalan, verifiying user name and password..registering your computer to the network.. bila berhasil konek akan muncul gambar monitor di

systray anda..

Bila error 734 : the ppp link control protocol has terminated terjadi, berarti anda belum bisa koneksi ke jaringan. Hal ini terjadi karena kita belum menambahkan parameter ke modem, tambahkan baris perintah at+cgdcont=1,”IP”,”www.indosat-m3.net” . Caranya, klik kanan my computer – properties – hardware – device manager – modems – pilih nokia 9300 usb modem, klik kanan – properties – dibagian advanced – extra settings masukkan baris perintah di situ – OK.

Coba dial sekali lagi. Mestinya udah konek.

Accessing and managing MS Excel sheets with Delphi

Accessing and managing MS Excel sheets with Delphi

Page 1: Methods for transferring data between Excel and Delphi. How to connect to Excel with ADO and Delphi.

How to retrieve, display and edit Microsoft Excel spreadsheets with ADO (dbGO) and Delphi. This step-by-step article describes how to connect to Excel, retrieve sheet data, and enable editing of data (using the DBGrid). You’ll also find a list of most common errors (and how to deal with them) that might pop up in the process.

Here’s what you will learn about in this (lengthy) article:

• Methods for transferring data between Excel and Delphi. How to connect to Excel with ADO and Delphi.
• Creating an Excel spreadsheet editor using Delphi and ADO
• Retrieving the data from Excel. How to reference a table (or range) in an Excel workbook.
• A discussion on Excel field (column) types
• How to modify Excel sheets: edit, add, and delete rows.
• Transferring data from a Delphi application to Excel. How to create a worksheet, and fill it with “custom” (from an Access database) data.

Connect to: MS Excel

Microsoft Excel is a powerful spreadsheet calculator and data analysis tool. Since rows and columns of an Excel worksheet closely relate to the rows and columns of a database table, many developers find appropriate to transport their data into an Excel workbook for analysis purposes; and retrieve data back to the application afterwards. The most commonly used approach to data exchange between your application and Excel is Automation. Automation provides a way to read Excel data using the Excel Object Model to dive into the worksheet, extract its data, and display it inside a grid-like component, namely DBGrid or StringGrid. Automation gives you the greatest flexibility for locating the data in the workbook as well as the ability to format the worksheet and make various settings at run time.

To transfer your data to and from Excel without Automation, you can use other methods such as:

Write data into a comma-delimited text file, and let Excel parse the file into cells,

Transfer data using DDE (Dynamic Data Exchange),

Transfer your data to (and from) a worksheet using ADO.

Data transfer using ADO

Since Excel is JET OLE DB compliant, you can connect to it with Delphi using ADO (dbGO or AdoExpress) then retrieve the worksheet’s data into an ADO dataset by issuing a SQL query – just like you would open a dataset against any database table. In this way, all the methods and features of the ADODataset object are available to process the Excel data. In other words, using the ADO components, you can build an application that can use an Excel workbook as the database. Another important fact is that Excel is an out-of-process ActiveX server. ADO runs in-process, and saves the overhead of costly out-of-process calls.When you connect to Excel using ADO, you can only exchange raw data to and from a workbook. ADO connection cannot be used for sheet formatting or implementing formulas to cells. However, if you transfer your data to a worksheet that is pre-formatted, the format is maintained. After the data is inserted from your application to Excel, you can carry out any conditional formatting using a (pre-recorded) macro in the worksheet.

You can connect to Excel using ADO with the two OLE DB Providers that are a part of MDAC: Microsoft Jet OLE DB Provider or Microsoft OLE DB Provider for ODBC Drivers. This article will focus on Jet OLE DB Provider which can be used to access data in Excel workbooks, through installable Indexed Sequential Access Method (ISAM) drivers.

If you are new to ADO, I suggest you to first read the “Beginners Course to Delphi ADO Database Programming“

The ConnectionString Magic

The ConnectionString property tells ADO how to connect to the datasource. The value used for ConnectionString consists of one or more arguments ADO uses to establish the connection. In Delphi, the TADOConnection component encapsulates the ADO connection object; it can be shared by multiple ADO dataset (TADOTable, TADOQuery, …) components through their Connection properties.In order to connect to Excel, a valid connection string involves only two (additional) pieces of information: the full path to the workbook, and the Excel file version. In other words, a legitimate connection string could look like:

ConnectionString := ‘Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\MyWorkBooks\myDataBook.xls;Extended Properties=Excel 8.0;’;

When you want to connect to an external database format supported by the Jet, you need to set the extended properties for the connection. In our case, when connecting to Excel “database”, extended properties are used to set the Excel file version.
For an Excel95 workbook this value is “Excel 5.0″ (without the quotes), for versions Excel 97, Excel 2000, Excel 2002 or ExcelXP the value is “Excel 8.0″.

Caution: you must use the Jet 4.0 Provider, since Jet 3.5 does not support the ISAM drivers. If you set the Jet Provider to version 3.5 you’ll receive the “Couldn’t find installable ISAM.” error message.

Another Jet extended property is “HDR=”. “HDR=Yes” means that there is a header row in the range, so the Jet will not include the first row of the selection into the dataset. If “HDR=No” is specified, then the provider will include the first row of the range (or named range) into the dataset. The first row in a range is considered to be the header row by default (“HDR=Yes”), therefore if you have column heading you do not need to specify this value. If you do not have column headings, you need to specify “HDR=No”;All set. This is the part where things become interesting; we are now ready for some code. Let’s see how to create a simple Excel Spreadsheet editor using Delphi and ADO…

Note: even if you lack knowledge on ADO and Jet programming, you should proceed. As you will see editing an Excel workbook is simple as editing data from any “standard” database!

From Zarko Gajic,
Your Guide to Delphi Programming.

Setting Up SQL 2005 Deployments – Migrating from SQL 2000

Setting up Microsoft SQL Server 2005 and migrating existing data from SQL 2000 is a relatively easy task if your implementation is enclosed and you do not touch default settings. There are, however many subtleties that can cause SQL migrations to go horribly wrong. If you understand the SQL Server model, and the changes that have been made to SQL Server, many of these problems can easily be side stepped.

In this entry, I’ll cover a few basic principals of SQL 2005 and a suggested path to migration so that you may avoid these steps.

Collation

First and most importantly, SQL 2005 has changed the “collation” model. Collation is essentially the comparisons on which indices get built and comparison operators operate. If you are not careful, changing collation during setup can cause a mess of problems when migrating SQL 2000 data. Although the internals of your database will operate without problems, new SQL 2005 databases will not be able to communicate and pull data from your migrated 2000 database.

This situation is cross deployment. If you have one SQL server running in one collation and another collation running in another, you may experience problems with log shipping, mirroring, and cross-database communications.

The SQL 2005 model has shifted, using a new model. SQL Analysis Services 2005 will not use the old collations at all, however the SQL server itself is capable of running databases in the SQL 2000 collations for backwards compatibility. If you are running in a mixed environment, I suggest that you setup your SQL 2005 servers to run in a backwards-compatible fashion. If you plan to migrate completely to 2005, I see no reason not to lose the SQL 2000 collation for the SQL 2005 collation; this will ensure that future upgrades will go by with much greater ease.

By default, SQL 2005 is configured to run in “SQL_Latin1_General_CI_AS”, or “SQL Server; Latin1 General; Case Insensitive; Accent Sensitive”. This and all other modes beginning with “SQL”, are SQL 2000 compatibility modes. If you need to configure SQL server to talk with 2000 database servers, the default mode is the one you want. If you want a clean SQL 2005 installation, the 2005 equivalent “Latin1_General_CI_AS” will serve you better.

Choosing the default collation mode is important, as it affects tempdb (the temporary tables), master, and all newly created databases. This is not a setting that should be overlooked.

Although the collation mode can be set on a database, object (stored procedure, table or even column level), I would recommend to sticking with a single collation mode. Multiple collation modes not only complicate deployments, but also cause comparison issues across data fields. The only scenario where I can see a collation-specific object necessary is in locations that handle things like case-sensitive passwords. There you may want to have a CS (case sensitive) collation. There are however, better ways of achieving case-sensitivity for those types of comparisons.

Database Compatibility Mode

SQL Server 2005 is capable of running in several “database compatibility modes”, allowing 2000 and 7.0 databases to run within a SQL 2005 instance. This compatibility mode has benefits, but will restrict your feature use (such as .NET UDT’s) when running in down-level versions. If you will be performing any transactions where SQL 2000 will be manipulating or requesting your SQL 2005 data, you may want to run the SQL 2005 database in a backwards-compatible mode to ensure that queries will run. If you are working in a full SQL 2005 deployment, the compatibility mode should be set to “SQL Server 9.0” (2005).

Database compatibility mode can be accessed by right clicking on a database in the SQL Server Management Studio, clicking properties, then the “options” tab.

SQL Authentication, Mixed Mode and Windows Authentication

Note that it is suggested that you utilize “Windows Authentication” mode in your SQL deployments unless you have reason otherwise. This is the most secure implementation. Mixed mode will work fine (and I use it in my deployment for reasons I won’t explain here), but note that you will be creating Windows and/or Domain accounts to achieve things such as SSIS (formally DTS) and scheduled jobs.

Deployment and Migration

Deploying SQL Server 2005 and migrating data from SQL 2000 is not a difficult task, but if you wish to modify collations and compatibility modes of your databases, this deployment process must be done carefully. Although backing up your database on 2000 and restoring it on 2005 works, changes in collation mode and other SQL 2005 changes may cause unexpected problems. It is best to do a clean migration as I have described in this document. This will ensure your transition from SQL 2000 to SQL 2005 is smooth and your databases are consistent.

My migration solution includes 4 basic steps:

• Install SQL 2005 and set collation modes correctly.
• Script SQL 2000 databases.
• Execute CREATE scripts on the SQL 2005 instance.
• Import data from the SQL 2000 databases into the newly created SQL 2005 databases.

Pre-Install

Ensure you backup your SQL 2000 databases and uninstall SQL 2000 before continuing.

Installing SQL

SQL Installation is fairly straightforward, and I will not document it in detail. I would like to note however, that it is useful to start ALL SQL services after the installation is complete, and that you will need to choose your collation settings at this point. Use my guide and description above to gear collation towards your needs.

Setup Your Existing Databases

Setting up your existing databases is where the fun begins. For this example, I will be focusing on deployment on same-machine. New machine deployments will be handled in a very similar fashion so this is still a good guide (a few extra steps are required for same-machine deployments. This setup assumes that you will want to upgrade your databases to SQL 9.0 (2005) compatibility mode (so that you can use 2005-specific features).

1. Add any existing SQL logins you have in 2000 to the logins in SQL 2005. You don’t need to configure their databases, but rather ensure they exist.
2. Load your database backup into the new SQL 2005 installation with a new name. The name of the database and location it is to be stored should not be equal to the final location of the database.
3. Run “EXEC sp_change_users_login update_one [@UserNamePattern] [@LoginName]” for each user in the database so that they are mapped back to their SQL Login in the new setup. This will ensure that all objects (including users) are scripted. More information on sp_change_users_login can be found here: http://www.transactsql.com/html/sp_change_users_login.html
4. Right click on your database, and choose “Properties”.
5. Click the “Options” tab and ensure the database compatibility mode is set to SQL 9.0. This ensures all objects (including SQL users) are scripted.

6. Right click on the restored database, select “Tasks > Generate Scripts”.
7. Ensure the correct database is selected to script, and check “Script all objects in the selected database”.
8. Next, you are presented with a list in “Choose Script Options”. You will want to change:
   1. “Script Database Create” to true
   2. “Script Object-Level Permissions” to true
   3. “Script USE DATABASE” to true
   4. DO NOT set “Script Collation” to true.

9. Choose “Script to New Query Window” and execute the scripting process.
10. When the new window is opened do a find and replace in the document for your restored database name to the final database name.
11. Change the file paths in the “CREATE DATABASE” statement to reflect the final file path of the database.
12. Execute the script.
13. Refresh the databases in the object explorer and right click on the newly created database. Select “Tasks > Import Data”.
14. Choose “SQL Native Client” as your data source, the SQL 2005 machine name as the database, and “Windows Authentication”. Select the restored 2000 database.

    
    

15. Choose “SQL Native Client” for the destination, and ensure your final database is selected.
16. Select “Copy data from one or more tables of views”.
17. Select all tables, make sure no views are checked off.
    1. Check “Optimize for many tables”
    2. Check “Run in a transaction”
    3. NOTE: You may have to update timestamps/rowversions to not be copied (click “edit” on the mapping of a table, and set the destination of a column to “ignore”).

18. Click next and run the import process.

At this point, you should have a fully working SQL 2005 structured database!

After Thoughts

Many of the new SQL 2005 features are ones that an upgrade won’t give you full benefit of. You may want to consider creating a few .NET UDT’s for more complex fields in your database. This may help you eliminate an abundance of rows that comprise one value, or values stored in a non-standard format for comparison purposes (ex. The “Version” datatype cannot be stored as string and be compared with ‘<’ or ‘>’ ).

Also, one of the big advantages of SQL 2005 is schemas. If you are properly authenticating systems (not using ‘sa’ for everything), you may want to consider sectioning off your applications, or pieces of specific applications with schemas. This helps maintain data integrity, security, and overall cleanliness (gives some order to those long stored procedure lists.

That’s all for now. I’ll be touching on setting up replication and SSIS next!

Posted: Apr 11 2006, 11:21 PM by mrdecav | with 1 comment(s) Filed under: .NET/C# Development, On Software