27.1.16

Mengatasi Pesan "Your Windows License Will Expire Soon' Windows 8.1

Tiba-tiba, di Windows 8.1 muncul pesan yang muncul berulang-ulang. "Your Windows License Will Expire Soon", padahal Windows datang bersama laptop (OEM). Ternyata, setelah Googling, pesan ini bisa muncul karena error. Di tempat kita ini, meminta pertolongan kepada penjual komputer aja susah, apalagi harus mengontak produsennya.

Salah satu cara untuk mengatasi error "Your Windows License Will Expire Soon" pada Windows 8.1 saya temukan di Windowsreport.com. Saya paste-kan ke sini untuk koleksi kalau nanti diperlukan:

How to deal with ‘Your Windows License Will Expire Soon’ Error on Windows 8.1

If you bought a new device that comes pre-installed with Windows 8 and now you are getting the license error then it means that your key might be rejected (the license key is embedded in BIOS). The best will be to contact your manufacturer in order to ask for official assistance and they will walk you through the troubleshooting process.

You can also try to fix the ‘Your Windows License Will Expire Soon’ alert by running Task Manager on your computer (press and hold “Ctrl + Alt + Del” keyboard sequence). Then from Task Manager press on “processes” tab and find “explorer”. Right click on “explorer” and choose “close”; then click on “file” (within Task Manager) and choose “new task” and type “explorer.exe”. Your Windows UI will be displayed once more. At this point go to your Start Page and from there press “Wind + R” in order to launch the Run sequence; there enter cmd and press enter. In the cmd window type “slmgr –rearm”, press enter and reboot your device.


Similar, on your Windows 8.1 computer you should open the Run box (see the steps from above) where you should enter “gpedit.msc”. The Local Group Policy Editor window will be displayed; from there navigate towards “Computer Configuration – Administrative Templates – Windows Components – Windows Update” and double click on “Windows Update”. Up next just select “enable” within “No auto-restart…” and reboot your device.

By following these guidelines you should be able to fix the ‘Your Windows License Will Expire Soon’ alert on Windows 8.1. Do share your experience with us and if you have problems we will try to resolve the same as soon as possible.

17.12.15

Resend (Kirim Lagi) Email Outlook

Kadang-kadang email yang kita kirim tidak sampai kepada recipient karena berbagai hal, misalnya quota email recipient yang penuh, email server tujuan sedang bermasalah, "rejected" karena sesuatu hal, dan sebagainya.

Kita diminta untuk mengirim lagi (resend) email tersebut.

Cara resend email di Outlook adalah sebagai berikut:

  1. Buka folder "Sent Items" dimana copy email yang terkirim disimpan.
  2. Double-click (buka) email ke dalam jendela sendiri (pop-up).
  3. Pada ribbon, klik tab "Message".
  4. Pada group "Move", klik "Actions". Akan terbuka pilihan menu.
  5. Klik "Resend This Message".
Selesai.

31.7.15

Improve Integration Access to MySQL

Berikut ini beberapa tips dan solusi dari MySQL untuk pengguna MS Access.
Saya kutipkan langsung sesuai aslinya untuk menjadi dokumentasi di sini.

To improve the integration between Microsoft Access and MySQL through Connector/ODBC:
  • For all versions of Access, enable the Connector/ODBC Return matching rows option. For Access 2.0, also enable the Simulate ODBC 1.0 option.
  • Include a TIMESTAMP column in all tables that you want to be able to update. For maximum portability, do not use a length specification in the column declaration (which is unsupported within MySQL in versions earlier than 4.1).
  • Include a primary key in each MySQL table you want to use with Access. If not, new or updated rows may show up as #DELETED#.
  • Use only DOUBLE float fields. Access fails when comparing with single-precision floats. The symptom usually is that new or updated rows may show up as #DELETED# or that you cannot find or update rows.
  • If you are using Connector/ODBC to link to a table that has a BIGINT column, the results are displayed as #DELETED#. The work around solution is:
    • Have one more dummy column with TIMESTAMP as the data type.
    • Select the Change BIGINT columns to INT option in the connection dialog in ODBC DSN Administrator.
    • Delete the table link from Access and re-create it.
    Old records may still display as #DELETED#, but newly added/updated records are displayed properly.
  • If you still get the error Another user has changed your data after adding a TIMESTAMP column, the following trick may help you:
    Do not use a table data sheet view. Instead, create a form with the fields you want, and use that form data sheet view. Set the DefaultValue property for the TIMESTAMP column to NOW(). Consider hiding the TIMESTAMP column from view so your users are not confused.
  • In some cases, Access may generate SQL statements that MySQL cannot understand. You can fix this by selecting "Query|SQLSpecific|Pass-Through" from the Access menu.
  • On Windows NT, Access reports BLOB columns as OLE OBJECTS. If you want to have MEMO columns instead, change BLOB columns to TEXT with ALTER TABLE.
  • Access cannot always handle the MySQL DATE column properly. If you have a problem with these, change the columns to DATETIME.
  • If you have in Access a column defined as BYTE, Access tries to export this as TINYINT instead of TINYINT UNSIGNED. This gives you problems if you have values larger than 127 in the column.
  • If you have very large (long) tables in Access, it might take a very long time to open them. Or you might run low on virtual memory and eventually get an ODBC Query Failed error and the table cannot open. To deal with this, select the following options:
    • Return Matching Rows (2)
    • Allow BIG Results (8).
    These add up to a value of 10 (OPTION=10).
Some external articles and tips that may be useful when using Access, ODBC and Connector/ODBC:
Sumber: http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-usagenotes-apptips-microsoft-access.html

Write Conflict Access - MySQL

Jika sebelumnya saya sudah menginformasikan soal Write Conflict ketika migrasi database Access ke SQL Server, jika anda melakukan migrasi ke MySQL, Write Conflict tidak hanya muncul karena field bertipe bit yang bernilai Null, tetapi bisa terjadi karena berbagai sebab yang lain. Pengalaman saya, setelah saya mengatasi field bit dan keharusan adanya field bertipe TimeStamp (hasil searching kesana-kemari), Write Conflict masih muncul juga. Akhirnya ada yang memberi solusi, yaitu pada kotak ODBC, pilih opsi "Return matched rows instead of affected rows".

Oleh karena saya melakukan koneksi secara code VBA, saya tidak tahu bagaimana mengatur opsi tersebut dalam connection string. Untunglah ada yang memberi solusi untuk menggunakan "Option=4196355". Alhamdulillah, Write Conflict teratasi, walaupun saya belum tahu apakah opsi pada kotak ODBC tersebut sama dengan "Option=4196355".

Mudah-mudahan membantu.

17.6.15

Write Conflict Ketika Mengedit Record Table SQL Server

Ketika kita melakukan migrasi dari database Access ke SQL Server, ada hal kecil yang mengesalkan. Field bertipe Yes/No pada Access akan dikonversi menjadi bertipe "bit" pada SQL Server, dan jika field ini berisi Null maka pada Access akan ditampilkan sebagai 0.

Problem muncul ketika kita mengedit record, kita tidak bisa menyimpan record tersebut karena akan muncul pesan "Write Conflict".

Solusinya, field bertipe bit harus not allow Null dan diberi nilai default 0.

Good luck!