diff --git a/website/.gitignore b/website/.gitignore
new file mode 100644
index 00000000..96a70eee
--- /dev/null
+++ b/website/.gitignore
@@ -0,0 +1,3 @@
+/public/
+/resources/
+.hugo_build.lock
diff --git a/website/README.md b/website/README.md
new file mode 100644
index 00000000..277d65e3
--- /dev/null
+++ b/website/README.md
@@ -0,0 +1,21 @@
+# psqlODBC website
+
+The source of the psqlODBC website, built with [Hugo](https://gohugo.io/) and the [Hextra](https://imfing.github.io/hextra/) theme. Hextra is a Hugo module whose version is pinned in `go.mod`.
+
+## Building
+
+You need Hugo extended 0.146 or later, and Go, which Hugo uses to download the theme.
+
+```sh
+cd website
+hugo server        # serves the site at http://localhost:1313/
+hugo --minify      # builds the site into public/
+```
+
+## Where the content comes from
+
+- `content/` holds the pages.
+- The changelog is `Changelog.md` at the top of the repository, which `hugo.yaml` mounts at `/changelog/`.
+- The images and `.reg` files come from `docs/`, which the Windows installer and the source tarball also ship.
+
+Pages that moved keep their old addresses through `aliases` in their front matter, so a link such as `/docs/config.html` redirects to `/docs/configuration/`.
diff --git a/website/content/_index.md b/website/content/_index.md
new file mode 100644
index 00000000..1b4e41f4
--- /dev/null
+++ b/website/content/_index.md
@@ -0,0 +1,99 @@
+---
+title: psqlODBC
+layout: hextra-home
+cascade:
+  - target:
+      path: /changelog
+    title: Changelog
+    weight: 4
+    type: docs
+---
+
+{{< hextra/hero-headline >}}
+  psqlODBC
+{{< /hextra/hero-headline >}}
+
+{{< hextra/hero-subtitle >}}
+  The official PostgreSQL ODBC driver
+{{< /hextra/hero-subtitle >}}
+
+<div class="hx:mt-6 hx:mb-6">
+{{< hextra/hero-button text="Documentation" link="docs" >}}
+{{< hextra/hero-button text="Download" link="https://www.postgresql.org/ftp/odbc/releases/" style="background: none; color: inherit; border: 1px solid;" >}}
+</div>
+
+<div class="content">
+
+**psqlODBC** is the official PostgreSQL ODBC Driver. It is released under the [Library General Public Licence](https://opensource.org/license/lgpl-license-html/), or LGPL.
+
+Downloads are available in source and binary formats at the [PostgreSQL downloads site](https://www.postgresql.org/ftp/odbc/releases/)
+
+------------------------------------------------------------------------
+
+## psqlODBC Documentation
+
+The following documents contain various bits of useful information. Please send any additional documentation, or report errors/omissions to <pgsql-odbc@postgresql.org>
+
+- [Notes on the various configuration settings.](/docs/configuration/)
+- [Compiling psqlODBC on Win32 systems.](/docs/building-windows/)
+- [Compiling psqlODBC on Unix systems.](/docs/building-unix/)
+- [Frequently Asked Questions (FAQ).](/faq/)
+- [Release notes.](/changelog/)
+
+------------------------------------------------------------------------
+
+## psqlODBC HOWTOs
+
+The following HOWTOs have been contributed by various people. If you wish to add to the collection, please send your contribution to <pgsql-odbc@postgresql.org>
+
+- [Example based Mini-Howto on Accessing PostgreSQL from C#](/howto/csharp/)
+- [Example based Mini-Howto on Accessing PostgreSQL from Ch](/howto/ch/)
+- [Using large objects in Microsoft Access (notes from the original psqlODBC docs)](/howto/access-large-objects/)
+- [Example based Mini-Howto on using Microsoft Access VBA with PostgreSQL](/howto/access-vba/)
+- [Example based Mini-Howto on Accessing PostgreSQL from Visual Basic](/howto/visual-basic/)
+- [Example based Mini-Howto on Pgsql Large Objects Interface and Visual Basic](/howto/visual-basic-large-objects/)
+- [PostgreSQL and Business Objects](/howto/business-objects/)
+
+------------------------------------------------------------------------
+
+## psqlODBC Development
+
+Previously psqlODBC was developed and supported through the [pgsql-odbc@postgresql.org](http://www.postgresql.org/list/pgsql-odbc/) mailing list.
+
+However we have moved the project to [GitHub psqlODBC](https://github.com/postgresql-interfaces/psqlodbc) please file issues [here](https://github.com/postgresql-interfaces/psqlodbc/issues)
+
+We will continue to monitor the pgsql-odbc mailing list however it's preferable to use GitHub.
+
+You can browse the source code at the psqlODBC git repository at [postgresql-interfaces/psqlodbc](https://github.com/postgresql-interfaces/psqlodbc). The source for this website is at the [psqlodbc-www](http://git.postgresql.org/gitweb/?p=psqlodbc-www.git)
+
+git repository
+
+A backup of the old CVS repository can be found [here](/backups/psqlodbc-cvs.tar.bz2).
+
+------------------------------------------------------------------------
+
+## psqlODBC History
+
+The source code for this driver was originally adopted from version 0.20 of PostODBC. The authors at that time were Christian Czezatke and Dan McGuirk. Later it was maintained by Julie Ann Case.
+
+As part of a commercial research project, the developers at Insight Distributions System overhauled the driver. Their goal was to make the driver commercially viable. In keeping with the spirit with which the original source was acquired, Insight published their work at their website. Some time later and after some discussion with members of the PostgreSQL organization, psqlODBC was adapted as the part of the PostgreSQL source distribution. The driver continued to be maintained by Byron Nikolaidis, the developer at Insight who overhauled the driver for some time.
+
+The driver is currently maintained by a number of contributors to the PostgreSQL project.
+
+------------------------------------------------------------------------
+
+## Acknowledgements
+
+### OpenSSL
+
+This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (<http://www.openssl.org/>).
+
+### MIT Kerberos
+
+This product includes Kerberos software developed by the Massachusetts Institute of Technology (<http://web.mit.edu/kerberos/>):
+
+Copyright 1992-2004 by the Massachusetts Institute of Technology. All rights reserved.
+
+THIS SOFTWARE IS PROVIDED "AS IS", AND M.I.T. MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. By way of example, but not limitation, M.I.T. MAKES NO REPRESENTATIONS OR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE LICENSED SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
+</div>
diff --git a/website/content/docs/_index.md b/website/content/docs/_index.md
new file mode 100644
index 00000000..1040133d
--- /dev/null
+++ b/website/content/docs/_index.md
@@ -0,0 +1,6 @@
+---
+title: Documentation
+weight: 1
+---
+
+Configuring, building and using psqlODBC.
diff --git a/website/content/docs/building-unix.md b/website/content/docs/building-unix.md
new file mode 100644
index 00000000..ee345fd1
--- /dev/null
+++ b/website/content/docs/building-unix.md
@@ -0,0 +1,60 @@
+---
+title: "Compiling psqlODBC on Unix"
+weight: 3
+aliases:
+  - /docs/unix-compilation.html
+---
+
+Following psqlODBC's move away from the main PostgreSQL source tree, Peter Eisentraut was kind enough provide a build environment for us which is now included in psqlODBC tarballs.
+
+## Installation
+
+To install, just try something like:
+
+> 
+>     % tar -zxvf psqlodbc-xx.xx.xxxx.tar.gz
+>     % cd psqlodbc-xx.xx.xxxx
+>     % ./configure
+>     % make
+>     % make install
+
+The configure script will accept the following useful options:
+
+- --with-libpq=DIR postgresql path (mandatory)
+- --with-unixodbc=DIR path or direct odbc_config file (default:yes)
+- --with-iodbc=DIR path or direct iodbc-config file
+- --with-odbcver=VERSION change default ODBC version number \[0x0351\]
+- --enable-pthreads (thread-safe driver on some platforms)
+- --disable-unicode (build non-Unicode driver)
+- --help
+
+## Building a distribution
+
+### Prerequisites
+
+- Autoconf 2.59 or higher
+- Automake 1.9.2 (Lower versions are rejected, version 1.7 untested.)
+- Libtool 1.5.10 or higher
+- PostgreSQL source tree (9.0 branch)
+
+### Bootstrapping
+
+> 
+>     autoreconf -i
+
+You can run 'make maintainer-clean' to remove all the files this generates.
+
+### Building
+
+> 
+>     ./configure
+>     make
+>     make install
+
+configure has the same options that the PostgreSQL configure used to have for ODBC, namely --with-iodbc or --with-unixodbc
+
+### Making a Source Distribution
+
+'make dist' makes a file psqlodbc-xx.xx.xxxx.tar.gz. It's even better to use 'make distcheck', which runs a number of tests to see if the distribution is internally consistent.
+
+The distribution does not contain any Windows-specific files (\*.def, maybe others). If it is desired to include them, edit Makefile.am.
diff --git a/website/content/docs/building-windows.md b/website/content/docs/building-windows.md
new file mode 100644
index 00000000..9657fb46
--- /dev/null
+++ b/website/content/docs/building-windows.md
@@ -0,0 +1,225 @@
+---
+title: "Compiling psqlODBC on Windows"
+weight: 4
+aliases:
+  - /docs/win32-compilation.html
+---
+
+This page describes how to build the PostgreSQL ODBC Driver on Windows. There are three methods to build: from command line using nmake makefiles, from Powershell using MSBuild files, and from Visual Studio IDE.
+
+The following 3rd party software are required for the build:
+
+- Microsoft Windows SDK 7.0 (or later), or Microsoft Visual Studio C++ 2005 Edition (or later). Other compilers may work but have not been tested. Download the latest version from [Microsoft's download page](http://www.microsoft.com/downloads/)
+- PostgreSQL Client library (libpq.dll) and headers. Download the latest version from the [PostgreSQL Binaries Download page](http://www.enterprisedb.com/products-services-training/pgbindownload/).
+- WiX Toolset. Required for building the installer. Download the latest version from the [WiX Toolset website](http://wixtoolset.org/)
+
+## Building with Powershell and MSBuild
+
+      Using Powershell and MSBuild is recommended. 
+      In fact the binaries of official release are built using this mothod.
+
+      Currently 4 Windows Powershell scripts are provided for developers.
+
+      winbuild/BuildAll.ps1          - build all dlls for psqlodbc drivers using
+                       MSBuild.
+      winbuild/editConfiguration.ps1 - a GUI tool to set Build environment
+      winbuild/regress.ps1           - build regression test programs and run
+      installer/buildInstallers.ps1  - build installers(.msi and setup.exe)
+
+      Use Powershell console or Command Prompt to invoke scripts:
+
+      For example, to build the driver:
+
+      C:\psqlodbc\winbuild\> (Powershell) ./BuildAll.ps1 <options>
+     
+        or you can use the same functionality from Command Prompt using Windows
+        helper batch at the parent folder (..\). See ..\readme_winbuild.txt.
+     
+      C:\psqlodbc\> (Command Prompt) .\BuildAll.bat <options>
+
+      1. Please start a powershell console and set the ExecutionPolicy of
+         Powershell to RemoteSigned or Unrestricted.
+
+         You can get the ExecutionPolicy by typing
+
+        Get-ExecutionPolicy
+
+         When the ExecutionPolicy is "Restricted" or "AllSigned" then type e.g.
+
+        Set-ExecutionPolicy RemoteSigned
+
+         To see details about ExecutionPolicy, type
+
+        Get-Help about_Execution_Policies
+
+      2. You have to install one of the following.
+
+       . Visual Studio 2015 non-Express edtion or Express 2015 for Windows
+        Desktop
+       . Visual Studio 2013 non-Express edtion or Express 2013 for Windows
+        Desktop
+       . Visual Studio 2012 non-Express edtion or Express 2012 for Windows
+        Desktop
+       . Full Microsoft Visual C++ 2010
+       . Windows SDK 7.1
+
+         You have to include x64 development tools (bin, lib, include) as
+         well as x86 ones for the installation.
+
+         You can install multiple versions of VC++ and use them.
+         You can easily switch by specifying VCVersion parameter.
+
+      3. Setup Build environment
+
+         Please type
+
+        .\editConfiguration(.ps1)
+
+         and edit the setting of your environment especially the folders
+         you placed libpq related include/lib/bin files.
+
+         
+
+      4. Build
+
+         Please type
+
+        .\BuildAll(.ps1)
+
+         to invoke build operations.
+
+         If you installed both VC10 and VC12 and you'd like to compile
+         under VC10 environment, type
+
+            .\BuildAll(.ps1) -V(CVersion) 10.0
+
+         or set the value 10.0 to vcversion using ./editConfiguration.
+
+         To see details about the use of BuildAll, type
+
+        Get-Help .\BuildAll(.ps1) [-Detailed | -Examples | -Full]
+
+      5. Outputs of Build
+
+         The build can produce output in up to four directories for each of
+         the debug and release configurations:
+
+         - x64_Unicode_Release     the Unicode driver, 64-bit
+         - x86_ANSI_Release        the ANSI driver, 64-bit
+         - x86_Unicode_Release     the ANSI driver, 32-bit
+         - x86_ANSI_Release        the Unicode driver, 32-bit
+
+         For debug builds (-Configuration Debug) the directories are named with
+         Debug instead of Release but otherwise the same.
+
+         pgxalib.dll is only built for the multibyte/unicode version, as it is
+         the same for both unicode and ansi drivers.
+      
+      6. How to use drivers.
+
+         You can't use psqlodbc drivers at once you build the drivers.
+         Usually you have to install drivers using installers made by
+         installer/buildInstallers.ps1. buildInstallers.ps1 bundles
+         libpq and related libraries like ssleay32, libeay32 from the
+         PostgreSQL bin directory and MSVC runtime libraries compiled with.
+
+         However, it is painful for developers to build binaries, build
+         installers and install each time the source files are changed. 
+         It is recommended to use a special installation-less driver
+         (postgres_devw) registered by regress.ps1
+
+      7. Regression test in place
+
+         After BuildAll(.ps1), please type
+
+        .\regress(.ps1)
+
+         You have to neither install nor copy binaries.
+         By default, build 32-bit binaries from test sources and run the tests.
+         If you'd like to test 64-bit version, please type
+
+        .\regress(.ps1) -p(latform) x64
+
+         Please note the outputs(obj, exe etc) generated by build operations and
+         results of tests are placed in the directory winbuild/test_x86(test_x64
+         in case of 64-bit).
+
+      8. Installer
+         
+         To build the .msi installer file:
+
+         C:\psqlodbc\installer\> (Powershell) ./buildInstallers.ps1 <options>
+            or
+         C:\psqlodbc\> (Command Prompt) .\buildInstallers.bat <options>
+
+         By default, buildInstallers.ps1 builds bootstrapper program
+         psqlodbc-setup.exe together.
+
+         See ../installer/readme.txt in the source directory for details.
+
+    Troubleshooting:
+
+         Some documentation on dealing with Windows SDK installation issues
+         can be found on the related pg_build_win page:
+         https://github.com/2ndQuadrant/pg_build_win#troubleshooting
+
+## Building with nmake.exe
+
+Use NMAKE.exe to build the driver for the currently active target:\
+\
+`C:\psqlodbc\> nmake /f win64.mak <options>`\
+
+
+Despite the name, win64.mak is used to build both 32-bit and 64-bit binaries. With the Microsoft Windows SDK Command Prompt, you can switch between 32-bit and 64-bit target architectures with `setenv /x86` and `setenv /x64` commands. If using a Visual Studio Command Prompt you can start the x86 or x64 versions from the Start menu, or run `vcvarsall.bat` with appropriate options to switch architectures.
+
+To build the .msi installer file:\
+\
+`C:\psqlodbc\> nmake /f win64.mak installer`\
+\
+The resulting installer file goes to installer/x64 or installer/x86 directory.
+
+To build both 32-bit and 64-bit versions in one command:\
+\
+`C:\psqlodbc\> nmake /f win64.mak world`\
+
+
+The following build options may be used, either on the command line, or by creating a file called "windows-local.mak".
+
+|              |                                                          |
+|--------------|----------------------------------------------------------|
+| Variable     | Values                                                   |
+| CFG          | Release(default), or Debug                               |
+| PG_INC       | \$(PROGRAMFILES)\PostgreSQL\9.3\include                  |
+| PG_LIB       | \$(PROGRAMFILES)\PostgreSQL\9.3\lib                      |
+| SSL_INC      | C:\OpenSSL-Win32\include                                 |
+| SSL_LIB      | C:\OpenSSL-Win32\lib                                     |
+| ANSI_VERSION | no (If set to "yes", output dll name to psqlodbc30a.dll) |
+| MSDTC        | yes                                                      |
+
+1.  UNICODE is the default (psqlodbc35w.dll), unless ANSI_VERSION is selected (psqlodbc30a.dll)
+2.  libpq.dll is mandatory.
+3.  If MSDTC == Yes, "pgxalib.dll" is created.
+4.  If MSDTC is enabled, ANSI_VERSION also creates "pgenlista.dll", or UNICODE creates "pgenlist.dll".
+
+## IDE Method
+
+A Microsoft Visual Studio project file (and workspace) is included in the source tree.
+
+**psqlodbc.dsp** can be used with Microsoft Visual C++ 6.0.
+
+**psqlodbc.proj** and **psqlodbc.sln** can be used with Microsoft Visual C++ 2005 Edition (including the Express edition which can be downloaded free of charge from <http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/default.aspx>)
+
+Preparation before the build:
+
+1.  The Windows distribution of PostgreSQL will install the required headers and libraries into C:\Program Files\PostgreSQL\9.2
+2.  OpenSSL should be installed into C:\OpenSSL (OpenSSL binaries can be downloaded from <http://www.slproweb.com/products/Win32OpenSSL.html>)
+
+If you want to change the installation arrangement, it is necessary to edit the project settings.
+
+Note:
+
+The default build settings will create the following driver:
+
+1.  UNICODE support.
+2.  libpq is mandatory.
+3.  The driver filename is "psqlodbc35w.dll".
diff --git a/website/content/docs/configuration.md b/website/content/docs/configuration.md
new file mode 100644
index 00000000..d994190c
--- /dev/null
+++ b/website/content/docs/configuration.md
@@ -0,0 +1,141 @@
+---
+title: "psqlODBC Configuration Options"
+weight: 1
+aliases:
+  - /docs/config.html
+---
+
+## Advanced Options 1/3 Dialog Box
+
+- **DEFAULTS:** Press to this button restore the normal defaults for the settings described below.
+- **Recognize Unique Indexes:** Check this option.
+- **Use Declare/Fetch:** If true, the driver automatically uses declare cursor/fetch to handle SELECT statements and keeps 100 rows in a cache. This is mostly a great advantage, especially if you are only interested in reading and not updating. It results in the driver not sucking down lots of memory to buffer the entire result set. If set to false, cursors will not be used and the driver will retrieve the entire result set. For very large tables, this is very inefficient and may use up all the Windows memory/resources. However, it may handle updates better since the tables are not kept open, as they are when using cursors. This was the style of the old podbc32 driver. However, the behavior of the memory allocation is much improved so even when not using cursors, performance should at least be better than the old podbc32.
+- **CommLog (C:\psqlodbc_xxxx.log):** Log communications to/from the backend to that file. This is good for debugging problems.
+- **Parse Statements:** Tell the driver how to gather the information about result columns of queries, if the application requests that information before executing the query. See also *ServerSide Prepare* options.\
+  The driver checks this option first. If disabled then it checks the Server Side Prepare option.\
+  \
+  If this option is enabled, the driver will parse an SQL query statement to identify the columns and tables and gather statistics about them such as precision, nullability, aliases, etc. It then reports this information in SQLDescribeCol, SQLColAttributes, and SQLNumResultCols.\
+  \
+  When this option is disabled (the default), the query is sent to the server to be parsed and described. If the parser can not deal with a column (because it is a function or expression, etc.), it will fall back to describing the statement in the server. The parser is fairly sophisticated and can handle many things such as column and table aliases, quoted identifiers, literals, joins, cross-products, etc. It can correctly identify a function or expression column, regardless of the complexity, but it does not attempt to determine the data type or precision of these columns.
+- **Ignore Timeout:** Ignore SQL_ATTR_QUERY_TIMEOUT set using SQLSetStmtAttr(). Some tools issue SQLSetStmtAttr(.., SQL_ATTR_QUERY_TIMEOUT, ...) internally and sometimes it's difficult for users to change the value.
+- **MyLog (C:\mylog_xxxx.log):** Log debug messages to that file. This is good for debugging problems with the driver.
+- **Unknown Sizes:** This controls what SQLDescribeCol and SQLColAttributes will return as to precision for character data types (varchar, text, and unknown) in a result set when the precision is unknown. **This was more of a workaround for pre-6.4 versions of PostgreSQL not being able to return the defined column width of the varchar data type**.\
+  \
+  - *Maximum*: Always return the maximum precision of the data type.
+  - *Dont Know*: Return "Don't Know" value and let application decide.
+  - *Longest*: Return the longest string length of the column of any row. Beware of this setting when using cursors because the cache size may not be a good representation of the longest column in the cache.
+    \
+    *MS Access*: Seems to handle *Maximum* setting ok, as well as all the others.\
+    *Borland*: If sizes are large and lots of columns, Borland may crash badly (it doesn't seem to handle memory allocation well) if using *Maximum* size.
+
+  \
+- **Data Type Options:** affects how some data types are mapped:
+  - *Text as LongVarChar*: PostgreSQL TEXT type is mapped to SQLLongVarchar, otherwise SQLVarchar.
+  - *Unknowns as LongVarChar*: Unknown types (arrays, etc) are mapped to SQLLongVarChar, otherwise SQLVarchar
+  - *Bools as Char*: Bools are mapped to SQL_CHAR, otherwise to SQL_BIT.
+
+  \
+- **Max Varchar** The maximum precision of the Varchar and BPChar(char\[x\]) types. The default is 254 which actually means 255 because of the null terminator. Note, if you set this value higher than 254, Access will not let you index on varchar columns!
+- **Cache Size:**When using cursors, this is the row size of the tuple cache and the default is 100 rows. If not using cursors, this has no meaning.
+- **Max LongVarChar:** The maximum precision of the LongVarChar type. The default is 4094 which actually means 4095 with the null terminator. You can even specify (-4) for this size, which is the odbc SQL_NO_TOTAL value.
+- **SysTable Prefixes:** Additional prefixes of table names to regard as System Tables. Tables that begin with "pg\_" are always treated as system tables, even without this option. Separate each prefix with a semicolon (;)
+- **Batch Size:**Chunk size when executing batches with arrays of parameters. Setting 1 to this option forces one by one execution (the behavior before).
+
+## Advanced Options 2/3 Dialog Box
+
+- **ReadOnly:** Whether the datasource will allow updates.
+- **Show System Tables:** The driver will treat system tables as regular tables in SQLTables. This is good for Access so you can see system tables.
+- **LF \<-\> CR/LF conversion:** Convert Unix style line endings to DOS style.
+- **Updateable Cursors:** Enable updateable cursor emulation in the driver.
+- **Bytea as LO:** Allow the use of bytea columns for Large Objects.
+- **Row Versioning:** Allows applications to detect whether data has been modified by other users while you are attempting to update a row. It also speeds the update process since every single column does not need to be specified in the where clause to update a row. The driver uses the "xmin" system field of PostgreSQL to allow for row versioning. Microsoft products seem to use this option well. See the [faq](/faq/) for details on what you need to do to your database to allow for the row versioning feature to be used.
+- **Display Optional Error Message:** Display optional(detail, hint, statement position etc) error messages.
+- **True is -1:** Represent TRUE as -1 for compatibility with some applications.
+- **Server side prepare:**If set, the driver uses server-side prepared statements. See also *Parse Statement* option. Note that if a query needs to be described before execution, e.g. because the application calls SQLDescribeCol() or SQLNumResultCols() before SQLExecute(), the driver will send a Parse request to the server even if this option is disabled. In that case, the query that is sent to the server for parsing will have the parameter markers replaced with the actual parameter values, or NULL literals if the values are not known yet.
+- **Int8 As:** Define what datatype to report int8 columns as.
+- **Numeric As:** Specify the map from numeric items without precision to SQL data types. numeric(default), varchar, double or memo(SQL_LONGVARCHAR) can be specified.
+- **Extra Opts:** combination of the following bits.\
+  \
+    0x1: Force the output of short-length formatted connection string. Check this bit when you use MFC CDatabase class.\
+    0x2: Fake MS SQL Server so that MS Access recognizes PostgreSQL's serial type as AutoNumber type.\
+    0x4: Reply ANSI (not Unicode) char types for the inquiries from applications. Try to check this bit when your applications don't seem to be good at handling Unicode data.
+- **Level of rollback on errors:** Specifies what to rollback should an error occur.
+  - *Nop(0):* Don't rollback anything and let the application handle the error.
+  - *Transaction(1):* Rollback the entire transaction.
+  - *Statement(2):* Rollback the statement.
+    \
+    **Setup note: This specification is set up with the PROTOCOL option parameter.**\
+    \
+    PROTOCOL=7.4-(0\|1\|2)\
+    default value is Statement (it is Transaction for servers before 8.0).\
+    \
+- **OID Options:**
+  - *Show Column:* Includes the OID in SQLColumns. This is good for using as a unique identifier to update records if no good key exists OR if the key has many parts, which blows up the backend.
+  - *Fake Index:* This option fakes a unique index on OID. This is useful when there is not a real unique index on OID and for apps which can't ask what the unique identifier should be (i.e, Access 2.0).
+- **Connect Settings:** The driver sends these commands to the backend upon a successful connection.  It sends these settings AFTER it sends the driver "Connect Settings". Use a semi-colon (;) to separate commands. This can now handle any query, even if it returns results. The results will be thrown away however!
+- **TCP KEEPALIVE setting(by sec):** Specifies TCP keepalives setting.
+  - *disable:* Check when client-side TCP keepalives are not used.
+  - *idle time:* The number of seconds of inactivity after which TCP should send a keepalive message to the server.
+  - *interval:* The number of seconds after which a TCP keepalive message that is not acknowledged by the server should be retransmitted.
+
+  
+
+## Advanced Options 3/3 Dialog Box
+
+- **Allow connections urecoverable by MSDTC?:** How to test distributed transactions.
+  - *yes:* MSDTC is needless unless applications crash. So don't check the connectivity from MSDTC.
+  - *rejects sslmode verify-\[ca\|full\]:* reject ssl connections with verify-ca or verify-full mode because in those cases msdtc could hardly establish the connection.
+  - *no:* First confirm the connectivity from MSDTC.
+
+  \
+- **Libpq parameters:** Specify libpq connection parameters with conninfo style strings e.g. **sslrootcert=c:\\myfolder\\myroot sslcert=C:\\myfolder\\mycert sslkey=C:\\myfolder\\mykey**.\
+  Though host, port, dbname, user, password, sslmode, keepalives_idle or keepalive_interval parameters can be set using this(pqopt) option, the use is not recommended because they are ordinarily set by other options. When some settings for those parameters conflict with other ordinary options, connections are rejected.
+
+## Global settings Dialog Box
+
+This dialog allows you to specify pre-connection/default logging options
+
+- **CommLog (C:\psqlodbc_xxxx.log - Communications log):** Log communications to/from the backend to that file. This is good for debugging problems.
+- **MyLog (C:\mylog_xxxx.log - Detailed debug output):** Log debug messages to that file. This is good for debugging problems with the driver.
+- **MSDTCLog (C:\pgdtclog\mylog_xxxx.log - MSDTC debug output):** Log debug messages to that file. This is good for debugging problems with the MSDTC.
+- **Specification of the holder for log outputs:** Adjustment of write permission.
+
+## Manage DSN Dialog Box
+
+This dialog allows you to select which PostgreSQL ODBC driver to use for this connection. Note that this may not work with third party drivers.
+
+## How to specify as a connection option
+
+There is a method of specifying a connection option in a keyword strings.
+
+Example:VBA
+
+- **myConn = "ODBC;DRIVER={PostgreSQL Unicode};" & serverConn & \_\
+  "A0=0;A1=7.4;A2=0;A3=0;A4=0;A5=0;A6=;A7=100;A8=4096;A9=0;" & \_\
+  "B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;BI=-5;" & \_\
+  "C0=0;C2=dd\_;C4=1;C5=1;C6=1;C7=1;C8=1;C9=0;CA=verify-full;D1=30;D4=40;" & \_\
+  "D5={sslrootcert=C:\\myfolder\\myroot sslcert=C:\\myfolder\\mycert sslkey=C:\\myfolder\\mykey}"**
+
+Please refer to a [keyword list](/docs/connection-options/) for details.
+
+## Special characters and escaping in connection strings
+
+A value that contains characters with a special meaning (`;`, `=`, spaces or braces) must be escaped. It is important to understand that a connection string is processed by **two independent parsers**, each with its own escaping rules.
+
+### 1. The psqlODBC connection string
+
+The driver splits the keyword string on `;` (the attribute delimiter) and on the first `=` of each attribute. To include one of these characters, or a space, in a value, use one of the following:
+
+- **Braces:** enclose the whole value in `{ }`. A braced value may contain `;`, `=` and spaces. For example **PWD={my;odd=pass word}**. To include a literal closing brace `}` inside a braced value, double it as `}}`.
+- **Percent-encoding:** outside of braces the value is URL-decoded, so a space can be written as `+` or `%20`, and an arbitrary byte as `%`*`XX`* (two hex digits). For example **PWD=pass+word** or **PWD=pass%20word**.
+
+A backslash (`\`) has **no special meaning** in the psqlODBC connection string itself; it is passed through literally.
+
+### 2. The Libpq parameters (pqopt) value
+
+The **Libpq parameters** option (see Advanced Options 3/3 above) is passed on to libpq and parsed by it as a [conninfo string](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING), which has its own, different rules. Within this value libpq separates parameters by spaces, so to include a space (or other special character) in a libpq parameter value you use libpq's escaping:
+
+- **Backslash:** `\` escapes the following character, e.g. **sslcert=C:\\ my\\ folder\\ cert**.
+- **Single quotes:** enclose the value in `' '`, e.g. **sslcert='C:\my folder\cert'**. A literal single quote or backslash inside quotes is written as `\'` and `\\`.
+
+This is why, in the VBA example above, the libpq paths inside the `D5={...}` braces use backslashes: the braces are consumed by the psqlODBC parser (layer 1), and the contents are then handed to libpq (layer 2). The two layers can therefore both apply to the same value.
diff --git a/website/content/docs/connection-options.md b/website/content/docs/connection-options.md
new file mode 100644
index 00000000..5bd695f7
--- /dev/null
+++ b/website/content/docs/connection-options.md
@@ -0,0 +1,57 @@
+---
+title: "How to specify as a connection option"
+weight: 2
+aliases:
+  - /docs/config-opt.html
+---
+
+**How to specify as a connection option**
+
+|  |  |  |
+|----|----|----|
+| **Definition** | **Keyword** | Abbreviation |
+| Data source description | Description | Nothing |
+| Name of Server | Servername | Nothing |
+| Postmaster listening port | Port | Nothing |
+| User Name | Username | Nothing |
+| Password | Password | Nothing |
+| Debug flag | Debug | B2 |
+| Fetch Max Count | Fetch | A7 |
+| Socket buffer size | Socket | A8 |
+| Database is read only | ReadOnly | A0 |
+| Communication to backend logging | CommLog | B3 |
+| PostgreSQL backend protocol | Protocol | A1 |
+| Connect Settings (commands sent to backend on connection) | ConnSettings | A6 |
+| Recognize unique indexes | UniqueIndex | Nothing |
+| Unknown result set sizes | UnknownSizes | A9 |
+| Use Declare/Fetch cursors | UseDeclareFetch | B6 |
+| Text as LongVarchar | TextAsLongVarchar | B7 |
+| Unknowns as LongVarchar | UnknownsAsLongVarchar | B8 |
+| Bools as Char | BoolsAsChar | B9 |
+| Max Varchar size | MaxVarcharSize | B0 |
+| Max LongVarchar size | MaxLongVarcharSize | B1 |
+| Fakes a unique index on OID | FakeOidIndex | A2 |
+| Includes the OID in SQLColumns | ShowOidColumn | A3 |
+| Row Versioning | RowVersioning | A4 |
+| Show SystemTables | ShowSystemTables | A5 |
+| Parse Statements | Parse | C0 |
+| SysTable Prefixes | ExtraSysTablePrefixes | C2 |
+| Updateable Cursors | UpdatableCursors | C4 |
+| LF \<-\> CR/LF conversion | LFConversion | C5 |
+| True is -1 | TrueIsMinus1 | C6 |
+| Datatype to report int8 columns as | BI | Nothing |
+| Bytea as LO (longVarBinary) | ByteaAsLongVarBinary | C7 |
+| Use serverside prepare | UseServerSidePrepare | C8 |
+| Lower case identifier | LowerCaseIdentifier | C9 |
+| SSL mode | SSLmode | CA |
+| Extra options | AB | Nothing |
+| Abbreviate(simple setup of a recommendation value) | CX | Nothing |
+| TCP KEEPALIVE setting: idle time | KeepaliveTime | D1 |
+| TCP KEEPALIVE setting: interval | KeepaliveInterval | D2 |
+| Libpq parameters (a conninfo style string e.g. pqopt={sslcert=~/mycert sslkey=~/mykey} enclosed with braces in the case of connection strings) | Pqopt | D5 |
+| Numeric As: specify the map from numeric items without precision to SQL data types. 2(SQL_NUMERIC default), 8(SQL_DOUBLE), 12(SQL_VARCHAR) or -1(SQL_LONGVARCHAR) can be specified. | NumericAS | D6 |
+| Show optional error messages. | OptionalErrors | D7 |
+| Chunk size when executing batches for parameterized SQL statements with arrays of parameters. | BatchSize | D8 |
+| Ignore SQL_ATTR_QUERY_TIMEOUT set using SQLSetStmtAttr(). | IgnoreTimeout | D9 |
+
+\
diff --git a/website/content/docs/msdtc-tracing.md b/website/content/docs/msdtc-tracing.md
new file mode 100644
index 00000000..1747248a
--- /dev/null
+++ b/website/content/docs/msdtc-tracing.md
@@ -0,0 +1,22 @@
+---
+title: "MSDTC tracing"
+weight: 5
+---
+
+The files:
+
+- [msdtc_pgxalib_tracing_enable.reg](/files/msdtc_pgxalib_tracing_enable.reg)
+- [msdtc_pgxalib_tracing_disable.reg](/files/msdtc_pgxalib_tracing_disable.reg)
+
+are Windows Registry Editor files that can be opened to add registry entries that turn psqlODBC's tracing for the Microsoft Distributed Transaction Co-Ordinator (MSDTC) on and off.
+
+You must also create `C:\pgdtclog` and ensure NETWORKSERVICE has write permissions. (It will by default on most Windows installs). At time of writing the trace path is hard coded to this location.
+
+This tracing is separate to regular ODBC API tracing and to psqlODBC's "mylog" tracing. It only traces access to the XA transaction manager used by MSDTC when doing XA transaction co-ordination. You probably only need this if you're debugging issues with "In doubt" or "only failed to notify" transactions in MSDTC.
+
+If you're tracing XA transactions in MSDTC you probably also want to trace MSDTC its self. For that, see:
+
+- <http://msdn.microsoft.com/en-us/library/ms684379(v=vs.85).aspx>
+- <http://msdn.microsoft.com/en-us/library/ms678917(v=vs.85).aspx>
+
+Tests suggest that only some SDKs' versions of the tracefmt.exe tool required will work - I found that Windows SDK 7.1's worked, but Visual Studio Express for Desktop 2012's didn't. Your results may vary.
diff --git a/website/content/faq.md b/website/content/faq.md
new file mode 100644
index 00000000..677f8857
--- /dev/null
+++ b/website/content/faq.md
@@ -0,0 +1,462 @@
+---
+title: "psqlODBC FAQ"
+type: docs
+weight: 3
+aliases:
+  - /faq.html
+---
+
+Mailing lists may be useful when problems do not solve with these.\
+[Discussion of PostgreSQL's ODBC interface.](https://www.postgresql.org/list/pgsql-odbc/)
+
+The most recent version of this document can be viewed at <https://odbc.postgresql.org/faq.html>.
+
+------------------------------------------------------------------------
+
+## 1) General
+
+[1.1](#q1-1)) How do I submit an idea for a new feature or even a patch?\
+[1.2](#q1-2)) Do I even need to compile the driver to use it?\
+[1.3](#q1-3)) How do I install the driver?\
+[1.4](#q1-4)) What operating systems will the driver run on?\
+[1.5](#q1-5)) I've seen other PostgreSQL ODBC drivers out there. Which one is the right one?\
+[1.6](#q1-6)) How do I report a bug or other problems?
+
+## 2) Basics
+
+[2.1](#q2-1)) How do I setup a datasource?\
+[2.2](#q2-2)) What's the difference between a File DSN, System DSN, and User DSN?\
+[2.3](#q2-3)) How do I access more advanced driver and/or datasource options?\
+[2.4](#q2-4)) Where can I discover more information about ODBC errors?\
+[2.5](#q2-5)) There are 2 drivers installed - which should I use?
+
+## 3) Connections
+
+[3.1](#q3-1)) Why do I get a message like "Failed to authenticate client as Postgres user using unknown authentication type:be_recvauth: unrecognized message type: 65536" when I try to connect to a datasource?\
+[3.2](#q3-2)) Why do I get a message like "User authentication failed"?\
+[3.3](#q3-3)) What do I need to do to establish a connection to a database?\
+[3.4](#q3-4)) Does psqlODBC support encrypted login for connections?
+
+## 4) Advanced
+
+[4.1](#q4-1)) Why do characters with umlauts or accents, or other non-ASCII characters show up in some applications as '?'\
+[4.2](#q4-2)) What data types does the driver support?\
+[4.3](#q4-3)) How do I use the row versioning -OR- why do I get a message about no operator for xid and int4?\
+[4.4](#q4-4)) Can I use large objects or OLE?\
+[4.5](#q4-5)) Why does the PostgreSQL backend complain about running out of memory when some I browse tables with primary keys?\
+[4.6](#q4-6)) How do I get my application to recognize primary keys?
+
+## 5) Borland Applications
+
+[5.1](#q5-1)) What driver/datasource options work well with Borland products?\
+[5.2](#q5-2)) \# Why do varchar/char datatypes not appear with the correct precision in Borland DBExplorer -OR- why do all varchar/char precisions appear as 128?
+
+## 6) Microsoft Applications
+
+[6.1](#q6-1)) Why don't int4 based aggregates seem to work?\
+[6.2](#q6-2)) Why does Access force me specify the Data Source each time I run my SQL Pass-Thru query?\
+[6.3](#q6-3)) Why does MS Access sometimes complain about a GROUP BY or ORDER BY not being in the target list?\
+[6.4](#q6-4)) Why do I get 'Write Conflict - This record has been changed by another user since you started editing it' in Access 2000 and above?\
+[6.5](#q6-5)) With MS Access, why can't I index on text fields -OR- why do I get "Invalid field definition 'field'" in definition of index or relationship?\
+[6.6](#q6-6)) With MS Access, why can't I GROUP BY, ORDER BY, or even select WHERE, on columns which are of type "text"?\
+[6.7](#q6-7)) With MS Access, why do I see \#Deleted# in rows after some operations?\
+[6.8](#q6-8)) Installing psqlODBC on 64bit Windows.
+
+## 1) General
+
+### 1.1) How do I submit an idea for a new feature or even a patch? {#q1-1}
+
+You can send mail to <pgsql-odbc@postgresql.org>.
+
+### 1.2) Do I even need to compile the driver to use it? {#q1-2}
+
+Probably not. If you are using Windows, all you really need to do is download and run the Full distribution.
+
+### 1.3) How do I install the driver? {#q1-3}
+
+The easiest way to install the driver is to get the Full distribution. Just download, unzip and run the setup program program. The installation is a standard Windows Installer package that will guide you through the process. For future upgrades, the MSI distribution can be used. This is considerably smaller as it does not include the Windows Installer redistributable which you only need install once. The second option is to compile the driver yourself. If you are using this driver on a unix platform, this is currently your only option.
+
+### 1.4) What operating systems will the driver run on? {#q1-4}
+
+The psqlODBC executable is written and compiled to run on 32 bit Wintel platform. This includes Windows 95, 98, ME, NT, 2000 and XP. 16 bit applications are capable of using the 32 bit driver but only on these platforms.
+
+We do not distribute binaries for Unix. The source code, however has been ported to compile under Unix. There are two driver managers available for Unix, [UnixODBC](http://www.unixodbc.org/) and [iODBC](http://www.iodbc.org/).
+
+### 1.5) I've seen other PostgreSQL ODBC drivers out there. Which one is the right one? {#q1-5}
+
+This one! This is *the* official PostgreSQL ODBC driver.
+
+### 1.6) How do I report a bug or other problems? {#q1-6}
+
+You can send mail to pgsql-odbc@postgresql.org When you do, however, you should attach the following:
+
+- your ODBC driver version
+- your PostgreSQL database version
+- any error messages you saw on the screen
+- the debug log (mylog\_????.log) file (you will have to enable the mylog driver option)
+
+Before posting however, please ensure you are running the latest version of psqlODBC.
+
+## 2) Basics
+
+### 2.1) How do I setup a datasource? {#q2-1}
+
+For Windows, use the ODBC Administrator in Control Panel (in some releases it may be found in the Administrative Tools folder. Here you can add, modify, or delete data sources.
+
+### 2.2) What's the difference between a File DSN, System DSN, and User DSN? {#q2-2}
+
+System DSN's and User DSN's differ only in who can access them on the system. A File DSN, however, is not really a datasource. It is a file that contains all the connection parameters used to connect directly to an ODBC driver.
+
+### 2.3) How do I access more advanced driver and/or datasource options? {#q2-3}
+
+First, select your favorite datasource to configure. Then in the "PostgreSQL Driver Setup" dialog, select under "Options (Advanced)" either the Driver button or Datasource button. This will bring up another dialog box which contains options you can configure. Refer to the Configuration Help for information on all these options.
+
+### 2.4) Where can I discover more information about ODBC errors? {#q2-4}
+
+The ODBC driver has an option to log all direct communication (queries, updates, etc.) with the backend as well as error messages and notices in the commlog file. In addition, it now also logs any ODBC connection and statement errors in this file with detailed information. This is good for applications that give misleading, little, or no descriptive information when something goes wrong (VisData is a good example).
+
+### 2.5) There are 2 drivers installed - which should I use? {#q2-5}
+
+**PostgreSQL Unicode** is a Unicode enabled driver that will work well with modern versions of applications such as Microsoft Access, with character from a huge range of languages. You should use this driver with PostgreSQL databases encoded as 'UNICODE' (more precisely known as 'UTF-8' in PostgreSQL).
+
+**PostgreSQL ANSI** is an ANSI driver which is also able to handle some multibyte character sets such as EUC_JP, BIG5 and Shift-JIS. This driver should also be used with databases encoded using any of the LATIN charactersets.
+
+Note that some applications (notably Borland BDE) do not work properly with Unicode ODBC drivers. In this case, you must use the ANSI driver.
+
+## 3) Connections
+
+### 3.1) Why do I get a message like "Failed to authenticate client as Postgres user using unknown authentication type:be_recvauth: unrecognized message type: 65536" when I try to connect to a datasource? {#q3-1}
+
+This message comes from the PostgreSQL backend, most likely when there is a protocol mismatch between the ODBC driver and the backend. For example, if you are using PostgreSQL 6.2 as the backend and try to use the ODBC driver without correctly setting the protocol, this error will occur. You must check the "6.2 protocol" advanced datasource option in the ODBC driver configuration dialog.
+
+**Note:** If you're still running 6.x these days, you really, really, really should upgrade to 8.x as soon as possible!!
+
+### 3.2) Why do I get a message like "User authentication failed"? {#q3-2}
+
+Verify that the database you are trying to connect to exists and is accessible by you. Also, see the above question in regards to user name and password authentication.
+
+### 3.3) What do I need to do to establish a connection to a database? {#q3-3}
+
+ODBC Connection Checklist:
+
+- ODBC Driver Data Source Checks
+  - Valid and resolvable hostname.
+  - Valid port number (default is 5432).
+  - Valid and existing database name.
+  - Valid user name.
+  - Valid password for the specified user (required if pg_hba.config is set to password authenticate your client).
+
+  
+- PostgreSQL Server Checks
+  - Postmaster must be running.
+  - Postmaster must run with the -i option , or tcpip=true in postgresql.conf to allow remote connections.
+  - The pg_hba.conf file in /data directory must be configured to allow your remote host to connect.
+
+### 3.4) Does psqlODBC support encrypted login for connections? {#q3-4}
+
+Yes. psqlODBC supports "md5" encrypted logins, but not "crypt" logins. Keep in mind that after login, ODBC sends all queries in plain text, so all you're protecting is your password. Also, support for md5 logins was added in late 2001, so if you have an older version of psqlODBC you may need to update it.
+
+**Note:** As of version 08.01.002, psqlODBC now supports SSL encrypted connections.
+
+## 4) Advanced
+
+### 4.1) Why do characters with umlauts or accents, or other non-ASCII characters show up in some applications as '?' {#q4-1}
+
+You are probably using the **PostgreSQL Unicode** driver with non-Unicode, 8 bit data - for example, from one of the LATIN encodings. You should either use the **PostgreSQL ANSI** driver, or move your data to a Unicode database.
+
+### 4.2) What data types does the driver support? {#q4-2}
+
+The driver provides full support for all PostgreSQL standard data types. These are: bool, int2, int4, int8, float4, float8, date, time, abstime, datetime, timestamp, char, varchar, and text.
+
+There is partial support for all other data types. Examples of these: point, circle, box and arrays. String support only is provided for these non-standard types. In other words, they are returned as SQL_VARCHAR and can be displayed and updated like any other data type. The resulting behavior will probably vary some with each application and data type.
+
+In the case of int4\[\] and MS Access 97 it does an effective job. The array can be displayed and updated cleanly. Arithmetic is a little tricky. MS Access complains about "t.a\[1\]" in the query builder. It does not like the syntax and never sends it to the backend. The work around is to choose the SQL Pass-thru option. This will allow you to build expressions like "t.a\[0\] \* t.a\[1\]". The hassle is that every time you run the query in Access 97 it prompts you with a database connection dialog.
+
+MS Excel in combination w/ MS Query may provide a better solution. It passes every query through. I try to stay away from the more exotic types if I know I am going to expose them to the public.
+
+### 4.3) How do I use the row versioning -OR- why do I get a message about no operator for xid and int4? {#q4-3}
+
+Some of the operators are missing in some releases of PostgreSQL (anyone remember which?) so in order to use row versioning, you must overload the int4eq function for use with the xid type. Also, you need to create an operator to compare xid to int4. You must do this for each database you want to use this feature on. This will probably not be necessary in PostgreSQL 6.4 since it will be added. Here are the details:
+
+        create function int4eq(xid,int4)
+            returns bool
+            as ''
+            language 'internal';
+
+        create operator = (
+            leftarg=xid,
+            rightarg=int4,
+            procedure=int4eq,
+            commutator='=',
+            negator='<>',
+            restrict=eqsel,
+            join=eqjoinsel
+        );
+        
+
+### 4.4) Can I use large objects or OLE? {#q4-4}
+
+Large objects are mapped to LONGVARBINARY in the driver to allow storing things like OLE objects in Microsoft Access. Multiple SQLPutData and SQLGetData calls are usually used to send and retrieve these objects. The driver creates a new large object and simply inserts its 'identifier' into the respective table. However, since PostgreSQL uses an 'Oid' to identify a Large Object, it is necessary to create a new PostgreSQL type to be able to discriminate between an ordinary Oid and a Large Object Oid. Until this new type becomes an official part of PostgreSQL, it must be added into the desired database and looked up for each connection. The type used in the driver is simply called "lo" and here is the command used to create it:
+
+        create type lo (
+            internallength=4,
+            externallength=10,
+            input=int4in,
+            output=int4out,
+            default='',
+            passedbyvalue
+        );
+
+        create table employee (
+            id integer,
+            name varchar(30),
+            picture lo
+        );
+        
+
+Once this is done, simply use the new 'lo' type to define columns in that database. When the driver sees an 'lo' type, it will handle it as SQL_LONGVARBINARY.
+
+Another important note is that this new type is lacking in functionality. It will not cleanup after itself on updates and deletes, thus leaving orphans around and using up extra disk space. And currently, PostgreSQL does not support the vacuuming of large objects.
+
+It would not be too difficult to write a interim stand-alone cleanup process to run at some interval on the server. It is only a matter of searching pg_attribute for lo data type columns and building a list of lo's by querying each table that contains lo's. Then compare this list with with the xinv.\* in pg_class. The xinv.\* with out a pointer are orphans and should be dropped.
+
+Hopefully in the future, a real large object data type will be available as a base type. But for now, it sure is fun to stick a Word document, Visio document, or AVI of a dancing baby into a database column, even if you will fill up your server's hard disk after a while!
+
+### 4.5) Why does the PostgreSQL backend complain about running out of memory when some I browse tables with primary keys? {#q4-5}
+
+The Jet Database Engine (used by Access) and others can use "keysets" to access records. Depending on how many parts are in the key, performance can range from slow to crashing of the backend. Here is a keyset query using 10 rows (the typical keyset amount):
+
+        -- This is a 3 part key
+
+        select ... from foo where
+            (v1 = "?" AND v2 = "?" AND v3 ="?") OR -- line 1
+            (v1 = "?" AND v2 = "?" AND v3 ="?") OR -- line 2
+        ...
+            (v1 = "?" AND v2 = "?" AND v3 ="?") OR -- line 9
+            (v1 = "?" AND v2 = "?" AND v3 ="?")    -- line 10
+        
+
+The question marks are replaced with the key values
+
+Prior to PostgreSQL 6.4, this was a major problem. But there are at least 2 fixes in place for this as of 6.4. One of the fixes is called KSQO (Keyset Query Optimization). As of 6.4, the driver now turns this on by default, although this can be changed in the Advanced Driver options settings.
+
+### 4.6) How do I get my application to recognize primary keys? {#q4-6}
+
+SQLPrimaryKeys() is implemented in the driver. The driver queries the system tables in search of a unique index named with the using "{table}\_pkey". For Example:
+
+        create table foo (
+            id integer primary key,
+            data varchar(20)
+        );
+        
+
+## 5) Borland Applications
+
+### 5.1) What driver/datasource options work well with Borland products? {#q5-1}
+
+Consider setting the following advanced driver options if using Borland:
+
+- Check Text as LongVarchar
+- Uncheck Unknowns as LongVarchar
+- Parse Statements option: Enable it, if using a protocol earlier than PostgreSQL 6.4
+- Unknown Sizes Options: Set to "Longest"
+
+### 5.1) Why do varchar/char datatypes not appear with the correct precision in Borland DBExplorer -OR- why do all varchar/char precisions appear as 128? {#q5-1}
+
+When using the 6.4 protocol, this problem should not be an issue.
+
+Prior to the PostgreSQL 6.4 protocol, the backend did not return the size of varchar/char datatypes in a query result and Borland relies heavily on this for both simple queries and the data dictionary import. Therefore, there are several driver options that were developed to help out with this.
+
+- Parse Statements option -- driver parses the SQL statement and retrieves characteristics such as precision, nullability, aliases, etc. for the columns.
+- Unknown Sizes option -- "longest" will return the precision based on the longest data of all the rows in the result set.
+
+Currently, if the parse statements option is enabled, the parser will fallback on executing the statement if it cannot deal with a particular column. Therefore, it is a good idea to set the unknown sizes to "longest" as well.
+
+## 6) Microsoft Applications
+
+### 6.1) Why don't int4 based aggregates seem to work? {#q6-1}
+
+Some Aggregates such as sum(int4) and avg(int4) return results using the numeric datatype. This is perfectly legal according to the SQL spec and is done to prevent overflows and other problems, but unfortunately Microsoft's ActiveX Data Objects don't seem to like it. There are two workarounds:
+
+- Cast the result to an int4 e.g. SELECT avg(fieldname)::int4 FROM tablename
+- Set the ADO CursorLocation to AdUseClient. Note: This will produce a read only recordset.
+
+### 6.2) Why does Access force me specify the Data Source each time I run my SQL Pass-Thru query? {#q6-2}
+
+There is a way to specify a Data Source in the query properties so it doesn't ask you each time. Under the view menu, select properties. For the "ODBC Connect Str" property right after "ODBC;" add "DSN=\<your_datasource_name_here\>". You can also add other properties if you like such as "ODBC;DSN=my_dsn;UID=me;PWD=test".
+
+### 6.3) Why does MS Access sometimes complain about a GROUP BY or ORDER BY not being in the target list? {#q6-3}
+
+This message comes from the PostgreSQL backend. PostgreSQL currently requires fields in the ORDER BY and GROUP BY clauses to be included in the target list. However, this restriction has been lifted in PostgreSQL 6.4+
+
+Older versions of the Microsoft Jet Database Engine, that Access is built on, has some problems that can cause this to occur. Access will insist on throwing in an order by clause in a join query, even if you are not sorting on anything. Even with PostgreSQL 6.4+, the query may no longer error out, BUT it would be sorted in a way you may not want, and there would be no way to change it. To fix this problem, you need to update the Jet database engine to version 3.51. It is available at no charge from Microsoft. Click [here to download](http://www.microsoft.com/data) the latest Jet Engine from the Microsoft support site.
+
+### 6.4) Why do I get 'Write Conflict - This record has been changed by another user since you started editing it' in Access 2000 and above? {#q6-4}
+
+**Contributed by Michael Zedeler (michael.zedeler@tirush.dk)**
+
+If you get the following message: "Write Conflict - This record has been changed by another user since you started editing it. \[...\]" from Access 2000, its likely to be a problem that arises from differing standards between Access and PostgreSQL.
+
+From old times, according to some SQL standard, an empty space is by definition equal to NULL. This disposition has caused many grievances over the years, so PostgreSQL rectifies this by deviating from the standard. In PostgreSQL, NULL is NULL and the empty string is the empty string.
+
+So when Access retrieves a row from PostgreSQL with fields containing the empty string, it automatically translates them into NULL values. When you try updating this row, the query sent from Access 2000 to PostgreSQL will fail to update the row. An example:
+
+You have inserted the following row into table a:
+
+            id  | name----+-------------------------  1 | <- contains the empty string. Not NULL.
+        
+
+And then you retrieve the row using Access 2000, subsequently inserting the value "Smartypants" in the "name" field.
+
+You would expect Access 2000 to send the following query to PostgreSQL:
+
+` UPDATE a SET name = 'Smartypants' WHERE id = 1 AND name = '' `
+
+(The extra "AND name = ''" is included to avoid updates in case that some other user has already updated the given row.)
+
+But what Access 2000 actually sends is:
+
+` UPDATE a SET name = 'Smartypants' WHERE id = 1 AND name IS NULL `
+
+That query fails because NULL is not being treated as the empty string by PostgreSQL.
+
+**How to fix the problem**
+
+I haven't found any way around it, but to stop using empty strings in character fields.
+
+The problem only arises when other systems inserts data into PostgreSQL tables, so you'll have to make those systems start using NULL in stead of the empty string, where necessary. When Access 2000 inserts data, it will always translate the empty string into NULL, thus maintaining data that are consistent with the (old?) SQL standard.
+
+PostgreSQL 7.2 and above can cause similar problems but for different reasons:
+
+**Contributed by Sam Hokin (sam@ims.net)**
+
+The new PostgreSQL timestamp data type defaults to microsecond precision. This means that timestamp values are stored like 2002-05-22 09:00:00.123456-05. However, Access does not support the extra precision, so the value that Access uses is 2002-05-22 09:00:00-05. When one tries to update a record, one gets the error message above because the value that Access uses in its UPDATE query does not match the value in the PostgreSQL table, similar to the NULL vs. empty string conflict that is already reported in this FAQ entry.
+
+**How to fix the problem**
+
+The simple fix is to use timestamp(0) rather than timestamp. Otherwise, one must make sure that all timestamp values entered into the PostgreSQL table have zero fractional second value.
+
+Incidentally, this problem occurs in Access 97 as well as Access 2000.
+
+**Contributed by Steven Citron-Pousty (Steven.Citron-Pousty@yale.edu)**
+
+Another way around the issue noted here in access2k and 7.2 is to use a query behind your data view that excludes the timestamp columns. In our case the timestamps are autogenerated so we don't even need to see them. So if you don't need to edit the timestamp value hide the column by making a query without the data value.
+
+### 6.5) With MS Access, why can't I index on text fields -OR- why do I get "Invalid field definition 'field'" in definition of index or relationship? {#q6-5}
+
+Text fields are mapped to SQL_LONGVARCHAR by default. As a result MS Access treats these colomns as "Memo" types. The good news is that you can store up to the PostgreSQL block size limit in a text column. PostgreSQL has a tuple limit of just under 8k prior to version 7.1 which includes a new feature called TOAST which allows the storage of much larger strings.
+
+You can change the mapping of Text fields to SQL_VARCHAR by unchecking the Advanced driver option "Text as LongVarchar" under Data Type Options. This should allow text fields to be used but you will be limited to the maximum size of a varchar.
+
+### 6.6) With MS Access, why can't I GROUP BY, ORDER BY, or even select WHERE, on columns which are of type "text"? {#q6-6}
+
+Text fields are mapped to SQL_LONGVARCHAR by default. As a result MS Access treats these colomns as "Memo" types. The good news is that you can store up to the PostgreSQL block size limit in a text column. PostgreSQL has a tuple limit of just under 8k prior to version 7.1 which includes a new feature called TOAST which allows the storage of much larger strings.
+
+You can change the mapping of Text fields to SQL_VARCHAR by unchecking the Advanced driver option "Text as LongVarchar" under Data Type Options. This should allow text fields to be used.
+
+### 6.7) With MS Access, why do I see \#Deleted# in rows after some operations? {#q6-7}
+
+This commonly occurs if you have used numeric or int8 (bigint) columns as your primary key. In Access, an Int is a 16 bit value and a Long Int is a 32 bit value, unlike PostgreSQL in which an int is a 32 bit value and a bigint is 64 bit. Access sees the int8/numeric key as a floating point value, which it cannot use as a key. To resolve the problem, stick to int4 if you need numerical primary keys. For more intofmation, please see [Microsoft KB article \#128809](http://support.microsoft.com/default.aspx?scid=kb;en-us;128809).
+
+### 6.8) Installing psqlODBC on 64bit Windows {#q6-8}
+
+**Contributed by Mark Wood (mw@mcwood.co.uk)**
+
+Though you can install 32 bit ODBC drivers on Win X64 as usual, you can't configure 32-bit DSNs via oridinary control panel or ODBC datasource administrator.
+
+**How to configure 32 bit ODBC drivers on Win x64**
+
+Configure ODBC DSN from **%SystemRoot%\syswow64\odbcad32.exe. ** Click
+
+   Start-\>Run\
+   Enter: **%SystemRoot%\syswow64\odbcad32.exe**\
+   Hit return\
+\
+This looks the same as the driver manager you might run from the control panel, but is for managing 32bit drivers. If you run odbcad32.exe from the System32 directory, you are actually running the 64bit driver manager.\
+\
+**What is WOW64?**\
+I would probably remove the rest of the info if possible, and just include a link to more information on WOW64 - maybe\
+<http://msdn.microsoft.com/en-us/library/aa384274(v=VS.85).aspx> for example.\
+\
+**What's and why WOW64**\
+<http://forums.techarena.in/operating-systems/1160164.htm>\
+\
+WoW64 stands for "Windows on 64-bit Windows", and it contains all the 32-bit binary files required for compatibility, which run on top of the\
+64 bit Windows. So, yeah" it looks like a double copy of everything in System32 (which despite the directory name, are actually 64-bit binaries).\
+\
+If you are running 32 bit Windows then finding this SysWoW64 directory is a bit weird ...\
+\
+WOW64 knows that the Setup wizard is a 32-bit application running within an emulator. It also knows that 64- and 32-bit code cannot be mixed. As such, the WOW64 emulator aliases an alias to the \Windows\SysWOW64 folder. This means that any time a 32-bit application needs to read or write anything to or from the \Windows\System32 folder, the WOW64 emulator transparently redirects the request to the \Windows\SysWOW64 folder.\
+\
+Microsoft offers a set of 32 bit executables in the WoW(Windows on Windows) directory of the system, for a Windows Vista 64 bit Operating System.\
+\
+To setup DSN for 32-bit application you must use: **%WINDIR%\SysWOW64\odbcad32.exe**\
+\
+and for 64-bit application you must use: **%WINDIR%\System32\odbcad32.exe**\
+\
+So, to run a 32 bit application, we would need to modify the env PATH variable and put SysWOW64 before system32.\
+\
+Roughly the steps would be\
+1. Start **%windir%\SysWoW64\cmd.exe**\
+2. set **PATH=%systemroot%\SysWOW64;%PATH%**\
+3. Run the application.\
+4. After application has completed, reset PATH variable if required.\
+\
+Hope this was helpful.\
+Or, if the application can't be run from a shell then you could modify the PATH variable directly from System Properties \> Advanced Tab \> Environmental Variable \> System variable.\
+Edit the PATH variable accordingly and reboot the system for the changes to take effect.\
+\
+And also check the related threads :\
+\
+\* Adminpak SP2 , Windows Server x64 SP2\
+\<<http://forums.techarena.in/windows-x64-edition/810091.htm>\>\
+\* Need Help Registering DLLs\
+\<<http://forums.techarena.in/windows-x64-edition/804399.htm>\>\
+\* Certificate Services Web interface and Win2k3 x64/AMD64 edition\
+\<<http://forums.techarena.in/server-security/598973.htm>\>\
+\
+Documentation on what you can expect you registry to show after installation using postgresql dbc msi\
+\
+<http://archives.postgresql.org/pgsql-interfaces/2001-01/msg00177.php>\
+\
+There are two versions of the ODBC driver at ftp.postgresql.org: one is the full package including installer, the other is just the driver itself.\
+Once you have installed with installer once, you can upgrade by just copying new versions of the driver to windows\system.\
+If for some reason you cannot get the installer to work, you can do the install by hand with regedit.\
+\
+Find the key **HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI** and add the following:\
+\
+REGEDIT4\
+\
+**\[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\PostgreSQL\]\**
+"Setup"="C:\\WINDOWS\\SYSTEM\\PSQLODBC.DLL"\
+"Driver"="C:\\WINDOWS\\SYSTEM\\PSQLODBC.DLL"\
+"APILevel"="1"\
+"ConnectFunctions"="YYN"\
+"CommLog"="0"\
+"Optimizer"="0"\
+"DriverODBCVer"="02.00"\
+"FileUsage"="0"\
+"SQLLevel"="1"\
+"UsageCount"=dword:00000001\
+"Fetch"="100"\
+"UniqueIndex"="1"\
+"ReadOnly"="0"\
+"UseCursors"="0"\
+"UnknownSizes"="0"\
+"TextAsLongVarchar"="0"\
+"UnknownsAsLongVarchar"="0"\
+"MaxVarcharSize"="254"\
+"MaxLongVarcharSize"="4094"\
+"ConnSettings"=""\
+"UseDeclareFetch"="0"\
+"BoolsAsChar"="0"\
+"ExtraSysTablePrefixes"="dd\_;"\
+"Parse"="1"\
+"Ksqo"="1"\
+"CancelAsFreeStmt"="0"**\**
+\
+(Note: check the above paths for your system)\
+\
+Find the key **HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC** Drivers and add an entry "**PostgreSQL= Installed**".\
+\
+From the Desk of Mark Wood (mw@mcwood.co.uk ) 20100524
diff --git a/website/content/howto/_index.md b/website/content/howto/_index.md
new file mode 100644
index 00000000..9f9a9a86
--- /dev/null
+++ b/website/content/howto/_index.md
@@ -0,0 +1,8 @@
+---
+title: HOWTOs
+weight: 2
+cascade:
+  type: docs
+---
+
+Examples of using psqlODBC from applications and languages. These were contributed by users of the driver.
diff --git a/website/content/howto/access-large-objects.md b/website/content/howto/access-large-objects.md
new file mode 100644
index 00000000..d76c24f2
--- /dev/null
+++ b/website/content/howto/access-large-objects.md
@@ -0,0 +1,31 @@
+---
+title: "Access Large Objects"
+weight: 3
+aliases:
+  - /howto-accesslo.html
+---
+
+*Author: Unknown\
+Release Date: Unknown\
+Description: Using large objects in Microsoft Access (notes from the original psqlODBC docs)*\
+
+
+## Using Large Objects for handling LongVarBinary (OLE Objects in Access)
+
+Large objects are mapped to LONGVARBINARY in the driver to allow storing things like OLE objects in Microsoft Access. Multiple SQLPutData and SQLGetData calls are usually used to send and retrieve these objects. The driver creates a new large object and simply inserts its 'identifier' into the respective table. However, since PostgreSQL uses an 'Oid' to identify a Large Object, it is necessary to create a new PostgreSQL type to be able to discriminate between an ordinary Oid and a Large Object Oid. Until this new type becomes an official part of PostgreSQL, it must be added into the desired database and looked up for each connection. The type used in the driver is simply called "lo" and here is the command used to create it:
+
+> 
+>     create type lo (
+>         internallength=4,
+>         externallength=10,
+>         input=int4in,
+>         output=int4out,
+>         default='',
+>         passedbyvalue
+>     );
+
+Once this is done, simply use the new 'lo' type to define columns in that database. Note that this must be done for each database you want to use large objects in with the driver. When the driver sees an 'lo' type, it will handle it as LONGVARBINARY.
+
+Another important note is that this new type is lacking in functionality. It will not cleanup after itself on updates and deletes, thus leaving orphans around and using up extra disk space. And currently, PostgreSQL does not support the vacuuming of large objects. Hopefully in the future, a real large object data type will be available.
+
+But for now, it sure is fun to stick a Word document, Visio document, or avi of a dancing baby into a database column, even if you will fill up your server's hard disk after a while!
diff --git a/website/content/howto/access-vba.md b/website/content/howto/access-vba.md
new file mode 100644
index 00000000..d01ba20e
--- /dev/null
+++ b/website/content/howto/access-vba.md
@@ -0,0 +1,154 @@
+---
+title: "Access VBA"
+weight: 2
+aliases:
+  - /howto-accessvba.html
+---
+
+*Author: Mark A. Taff (mark@libertycreek.net)\
+Release Date: 12 February 2002\
+Description: Example based Mini-Howto on using Microsoft Access VBA with PostgreSQL*\
+\
+Here is some VBA code I have written as it can be hard to find answers related to the PostgreSQL ODBC driver. Specifically, how to programmatically link and unlink PostgreSQL relations in a MS Access database. This is tested with Access 2000 on win2k with PostgreSQL 7.1.3 on Red Hat 7.2.\
+\
+The tricky thing here is the special way to specify the Connection parameters so Access will accept them in the context of an Access table definition object (as opposed to an ADODB connection object). The code is heavily commented to explain it, and consists of two subroutines, one to link a new relation and another to unlink it.\
+\
+I am making it available for public knowledge WITHOUT ANY WARRANTY, but I sure hope it makes someone else's life a bit easier.
+
+## Code
+
+> 
+>
+>     Private Sub Link_ODBCTbl(serverConn As String, rstrTblSrc As String, _
+>                              rstrTblDest As String, db As Database) 
+>     LogEvent "Entering " & APP_NAME & ": Form_Login.Link_ODBCTbbl(" & _
+>              rstrTblSrc & ")", etDebug 
+>     On Error GoTo Err_Handler
+>
+>     StartWork "Adding relation: " & rstrTblSrc
+>
+>         Dim tdf As TableDef
+>         Dim connOptions As String
+>         Dim myConn As String
+>         Dim myLen As Integer
+>         Dim bNoErr As Boolean
+>
+>         bNoErr = True
+>
+>         Set tdf = db.CreateTableDef(rstrTblDest)
+>         ' don't need next line, as only called if doesn't exist locally
+>         'db.TableDefs.Delete rstrTblDest 
+>         ' this is 1st error, as doesn't exist locally yet; maybe wrong key
+>
+>
+>     ' The length of the connection string allowed is limited such that you can't 
+>     ' specify all of the PostgreSQL ODBC driver options as you normally would. 
+>     ' For those that want to do it normally, you are limited to somewhere between 
+>     ' 269 characters (works) and 274 (doesn't work). Using a dsn is not a workaround. 
+>     ' 
+>     ' ***WORKAROUND*** Tested Access 2000 on Win2k, PostgreSQL 7.1.3 on Red Hat 7.2 
+>     ' 
+>     ' The connection string begins as usual, for example: 
+>     '
+>     '   "ODBC;DRIVER={PostgreSQL};DATABASE=database_name_to_connect_to;" & _
+>     '   "SERVER=ip_address_to_connect_to;PORT=5432;Uid=username_to_connect_as;" & _
+>     '   "Pwd=password_of_user;" & _ 
+>     ' 
+>     ' For all other parameters, you must code them in the same way Access stores them 
+>     ' in the hidden MSysObjects table.  Here is a cross-reference table: 
+>     ' 
+>     '   PG_ODBC_PARAMETER           ACCESS_PARAMETER
+>     '   *********************************************
+>     '   READONLY                    A0
+>     '   PROTOCOL                    A1
+>     '   FAKEOIDINDEX                A2  'A2 must be 0 unless A3=1
+>     '   SHOWOIDCOLUMN               A3
+>     '   ROWVERSIONING               A4
+>     '   SHOWSYSTEMTABLES            A5
+>     '   CONNSETTINGS                A6
+>     '   FETCH                       A7
+>     '   SOCKET                      A8
+>     '   UNKNOWNSIZES                A9  ' range [0-2]
+>     '   MAXVARCHARSIZE              B0
+>     '   MAXLONGVARCHARSIZE          B1
+>     '   DEBUG                       B2
+>     '   COMMLOG                     B3
+>     '   OPTIMIZER                   B4  ' note that 1 = _cancel_ generic optimizer...
+>     '   KSQO                        B5
+>     '   USEDECLAREFETCH             B6
+>     '   TEXTASLONGVARCHAR           B7
+>     '   UNKNOWNSASLONGVARCHAR       B8
+>     '   BOOLSASCHAR                 B9
+>     '   PARSE                       C0
+>     '   CANCELASFREESTMT            C1
+>     '   EXTRASYSTABLEPREFIXES       C2
+>     '
+>     ' So the parameter part of the connection string might look like: '
+>     '   "A0=0;A1=6.4;A2=0;A3=0;A4=0;A5=0;A6=;A7=100;A8=4096;A9=0;" & _
+>     '   "B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;C0=0;C1=0;C2=dd_"
+>     '
+>     ' Concatenating those four strings together will give you a working connection  
+>     ' string (but you may want to change the options specified). 
+>     ' 
+>     ' NOTES:
+>     '   `Disallow Premature` in driver dialog is not stored by Access.
+>     '   string must begin with `ODBC;` or you will get error
+>     '   `3170 Could not find installable ISAM`.
+>
+>     'Debug.Print svr.Conn
+>
+>     myConn = "ODBC;DRIVER={PostgreSQL};" & serverConn & _
+>                 "A0=0;A1=6.4;A2=0;A3=0;A4=0;A5=0;A6=;A7=100;A8=4096;A9=0;" & _
+>                 "B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;" & _
+>                 "C0=0;C1=0;C2=dd_"
+>
+>         tdf.Connect = myConn
+>         tdf.SourceTableName = rstrTblSrc
+>         db.TableDefs.Append tdf
+>         db.TableDefs.Refresh
+>
+>         ' If we made it this far without errors, table was linked...
+>         If bNoErr Then
+>             LogEvent "Form_Login.Link_ODBCTbl: Linked new relation: " & _
+>                      rstrTblSrc, etDebug
+>         End If
+>
+>         'Debug.Print "Linked new relation: " & rstrTblSrc ' Link new relation
+>
+>         Set tdf = Nothing
+>
+>     Exit Sub
+>
+>     Err_Handler:
+>         bNoErr = False
+>         Debug.Print Err.Number & " : " & Err.Description
+>         If Err.Number <> 0 Then LogError Err.Number, Err.Description, APP_NAME & _
+>                                          ": Form_Login.Link_ODBCTbl"
+>         Resume Next
+>
+>     End Sub
+>
+>     Private Sub UnLink_ODBCTbl(rstrTblName As String, db As Database) 
+>     LogEvent "Entering " & APP_NAME & ": Form_Login.UnLink_ODBCTbbl", etDebug 
+>     On Error GoTo Err_Handler
+>
+>         StartWork "Removing revoked relation: " & rstrTblName
+>
+>         ' Delete the revoked relation...that'll teach 'em not to get on my bad side
+>         ' I only call this sub after verifying the relation exists locally, so I 
+>         ' don't check if it exists here prior to trying to delete it, however if you 
+>         ' aren't careful...
+>         db.TableDefs.Delete rstrTblName
+>         db.TableDefs.Refresh
+>
+>         Debug.Print "Removed revoked relation: " & rstrTblName
+>
+>     Exit Sub
+>
+>     Err_Handler:
+>         Debug.Print Err.Number & " : " & Err.Description
+>         If Err.Number <> 0 Then LogError Err.Number, Err.Description, APP_NAME & _
+>                                          ": Form_Login.UnLink_ODBCTbl"
+>         Resume Next
+>
+>     End Sub
diff --git a/website/content/howto/business-objects.md b/website/content/howto/business-objects.md
new file mode 100644
index 00000000..202912c6
--- /dev/null
+++ b/website/content/howto/business-objects.md
@@ -0,0 +1,29 @@
+---
+title: "Business Objects"
+weight: 6
+aliases:
+  - /howto-bo.html
+---
+
+*Author: Peter S. Hamlen (phamlen@teachforamerica.org)\
+Release Date: 26 May 2003\
+Description: PostgreSQL and Business Objects*\
+\
+Will Postgresql ODBC work with Business Objects?\
+\
+Yes, with three caveats:
+
+1.  Technically, Business Objects does not support PostgreSQL. They do support generic ODBC access to databases, however.
+2.  You must change the ODBC parameter file on any machine that uses Designer. The ODBC file is usually *C:\Program Files\Business Objects\Data Access X.X\ODBC\ODBC10EN.PRM*. You must change the OWNER parameter to N and the QUALIFIER parameter to N (ie, OWNER=N, QUALIFIER=N).\
+    \
+    NOTE: It is only necessary to change this file for people who use Designer. BusinessObjects, WebIntelligence, and all other BO programs that use existing Universes are unaffected.
+3.  As with all other generic ODBC connections, you cannot do outer joins in Designer.
+
+Martín de la Herrán also adds the following notes:
+
+Also add the following parameters to C:\Program Files\Business Objects\Data Access X.X\ODBC\ODBC10EN.PRM\
+\
+BACK_QUOTE_SUPPORTED=Y\
+TABLE_DELIMITER="\
+\
+These parameters are necessary to use tables with spaces and unusual chararacters in them.
diff --git a/website/content/howto/ch.md b/website/content/howto/ch.md
new file mode 100644
index 00000000..9ae79d64
--- /dev/null
+++ b/website/content/howto/ch.md
@@ -0,0 +1,119 @@
+---
+title: "Ch"
+weight: 7
+aliases:
+  - /howto-ch.html
+---
+
+*Author: Wayne Cheng (wayne@softintegration.com)\
+Release Date: 23 September 2003\
+Description: Example based Mini-Howto on Accessing PostgreSQL from Ch*\
+\
+Ch is a C/C++ interpreter from <http://www.softintegration.com>.\
+It is designed for cross-platform scripting, shell programming, 2D/3D plotting, numerical computing, and embedded scripting.\
+\
+Requirements to get the code to work:
+
+- Ch Standard Edition or Professional Edition
+- Ch ODBC Toolkit.
+- IODBC, UNIXODBC or Microsoft ODBC manager.
+- A PostgreSQL datasource.
+
+**How to run ODBC code in Ch**\
+You should be able to use the simple.c scripts, start Ch shell first.
+
+> 
+>     % ch
+>                                        Ch 
+>                       Standard edition, version 4.0.0.11291 
+>                   (C) Copyright 2001-2003 SoftIntegration, Inc.
+>                          http://www.softintegration.com
+>     /home/wcheng> cd $CHHOME/package/iodbc/demos
+>     /usr/local/ch/package/iodbc/demos> ls
+>     odbctest.c  simple.c
+>     /usr/local/ch/package/iodbc/demos> ./simple.c
+>     SQLAllocHandle() OK
+>     SQLSetEnvAttr() ok
+>     SQLAllocHandle() ok
+>     SQLSetConnectAttr() ok
+>     /usr/local/ch/package/iodbc/demos> cat simple.c
+>
+>     /**************************** simple.c *****************************/ 
+>     #include <sqlext.h>
+>     #include <stdio.h>
+>
+>     void ODBC_error (       /* Get and print ODBC error messages */
+>         SQLHENV henv,       /* ODBC Environment */
+>         SQLHDBC hdbc,       /* ODBC Connection Handle */
+>         SQLHSTMT hstmt)     /* ODBC SQL Handle */
+>     {
+>         UCHAR   sqlstate[10];
+>         UCHAR   errmsg[SQL_MAX_MESSAGE_LENGTH];
+>         SDWORD  nativeerr;
+>         SWORD   actualmsglen;
+>         RETCODE rc = SQL_SUCCESS;
+>
+>         while ( rc != SQL_NO_DATA_FOUND)
+>         {
+>             rc = SQLError(henv, hdbc, hstmt,
+>                           sqlstate, &nativeerr, errmsg,
+>                           SQL_MAX_MESSAGE_LENGTH - 1, &actualmsglen);
+>                          
+>              if (rc == SQL_ERROR) {
+>                   printf ("SQLError failed!\n");
+>                   return;
+>              }
+>
+>              if (rc != SQL_NO_DATA_FOUND) {
+>                    printf ("SQLSTATE = %s\n", sqlstate);
+>                    printf ("NATIVE ERROR = %d\n", nativeerr);
+>                    errmsg[actualmsglen] = '\0';
+>                    printf ("MSG = %s\n\n", errmsg);
+>               }
+>          }
+>          if (hdbc != SQL_NULL_HDBC)
+>          {
+>             SQLFreeHandle (SQL_HANDLE_DBC, hdbc);
+>          }
+>          if (henv != SQL_NULL_HENV)
+>          {
+>             SQLFreeHandle (SQL_HANDLE_ENV, henv);
+>          }
+>     }
+>
+>     int main(void)
+>     {
+>         SQLHENV henv = SQL_NULL_HENV;
+>         SQLHDBC hdbc = SQL_NULL_HDBC;
+>         SQLHSTMT hstmt = SQL_NULL_HSTMT;
+>         RETCODE  rc    = SQL_SUCCESS;
+>
+>         rc = SQLAllocHandle (SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv);
+>
+>         if (rc != SQL_ERROR)
+>         {
+>             printf("SQLAllocHandle() OK\n");
+>             rc = SQLSetEnvAttr(henv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER)SQL_OV_ODBC3,0);
+>             if (rc != SQL_ERROR)
+>             {
+>                 printf("SQLSetEnvAttr() ok\n");
+>                 rc = SQLAllocHandle (SQL_HANDLE_DBC, henv, &hdbc);
+>                 if ( rc != SQL_ERROR)
+>                 {
+>                      printf("SQLAllocHandle() ok\n");
+>                      rc = SQLSetConnectAttr(hdbc, SQL_ATTR_AUTOCOMMIT, SQL_AUTOCOMMIT_OFF,0);
+>                      if (rc != SQL_ERROR)
+>                      {
+>                            printf("SQLSetConnectAttr() ok\n");
+>                            SQLFreeHandle(SQL_HANDLE_DBC, hdbc);
+>                            SQLFreeHandle(SQL_HANDLE_ENV, henv);
+>                      }
+>                  }
+>              }
+>          }
+>
+>          if (rc == SQL_ERROR)
+>          {
+>              ODBC_error (henv, hdbc, hstmt);
+>          }
+>     }
diff --git a/website/content/howto/csharp.md b/website/content/howto/csharp.md
new file mode 100644
index 00000000..16bddd4a
--- /dev/null
+++ b/website/content/howto/csharp.md
@@ -0,0 +1,101 @@
+---
+title: "C#"
+weight: 1
+aliases:
+  - /howto-csharp.html
+---
+
+*Author: Dave Page (dpage@postgresql.org)\
+Release Date: 12 April 2002\
+Description: Example based Mini-Howto on Accessing PostgreSQL from C#*\
+\
+This document provides some sample code to get you started with C# & PostgreSQL.\
+\
+Requirements to get the code to work:
+
+- A C# Compiler.
+- The Microsoft .NET Framework.
+- The Microsoft ODBC .NET Data Provider.
+- A PostgreSQL datasource.
+
+The example code shown below may need some modification to make it actually work in your environment. There is one table used in the example:
+
+> 
+>     CREATE TABLE vbtest(
+>         id serial,
+>         data text,
+>         accessed timestamp
+>     );
+>     INSERT INTO csharptest(data, accessed) VALUES('Rows: 1', now());
+>     INSERT INTO csharptest(data, accessed) VALUES('Rows: 2', now());
+>     INSERT INTO csharptest(data, accessed) VALUES('Rows: 3', now());
+
+## Code
+
+> 
+>
+>     using System;
+>     using System.Data;
+>     using Microsoft.Data.Odbc;
+>      
+>
+>     class psqlODBC_Howto
+>     {
+>
+>       [STAThread]
+>       static void Main(string[] args)
+>       {
+>
+>         // Setup a connection string
+>         string szConnect = "DSN=dsnname;" +
+>                            "UID=postgres;" +
+>                            "PWD=********";
+>
+>         // Attempt to open a connection
+>         OdbcConnection cnDB = new OdbcConnection(szConnect);
+>          
+>         // The following code demonstrates how to catch & report an ODBC exception.
+>         // To keep things simple, this is the only exception handling in this example.
+>         // Note: The ODBC data provider requests ODBC3 from the driver. At the time of
+>         //       writing, the psqlODBC driver only supports ODBC2.5 - this will cause
+>         //       an additional error, but will *not* throw an exception.
+>         try 
+>         {
+>           cnDB.Open();
+>         } 
+>         catch (OdbcException ex) 
+>         {
+>           Console.WriteLine (ex.Message + "\n\n" + "StackTrace: \n\n" + ex.StackTrace);
+>           // Pause for the user to read the screen.
+>           Console.WriteLine("\nPress  to continue...");
+>           Console.Read();
+>           return;
+>         }
+>         
+>         // Create a dataset
+>         DataSet dsDB = new DataSet(); 
+>         OdbcDataAdapter adDB = new OdbcDataAdapter();
+>         OdbcCommandBuilder cbDB = new OdbcCommandBuilder(adDB);
+>         adDB.SelectCommand = new OdbcCommand(
+>                                  "SELECT id, data, accessed FROM csharptest", 
+>                                  cnDB);
+>         adDB.Fill(dsDB);
+>
+>         // Display the record count
+>         Console.WriteLine("Table 'csharptest' contains {0} rows.\n", 
+>                           dsDB.Tables[0].Rows.Count);
+>         
+>         // List the columns (using a foreach loop)
+>         Console.WriteLine("Columns\n=======\n");
+>         
+>         foreach(DataColumn dcDB in dsDB.Tables[0].Columns)
+>           Console.WriteLine("{0} ({1})", dcDB.ColumnName, dcDB.DataType);
+>         Console.WriteLine("\n");
+>
+>         // Iterate through the rows and display the data in the table (using a for loop).
+>         // Display the data column last for readability.
+>         Console.WriteLine("Data\n====\n");
+>         for(int i=0;i to continue...");
+>         Console.Read();
+>       }
+>     }
diff --git a/website/content/howto/visual-basic-large-objects.md b/website/content/howto/visual-basic-large-objects.md
new file mode 100644
index 00000000..ad69476d
--- /dev/null
+++ b/website/content/howto/visual-basic-large-objects.md
@@ -0,0 +1,312 @@
+---
+title: "Visual Basic Large Objects"
+weight: 5
+aliases:
+  - /howto-vblo.html
+---
+
+*Author: Denis Gasparin (denis@edistar.com)\
+Release Date: 29 October 2001\
+Description: Example based Mini-Howto on Pgsql Large Objects Interface and Visual Basic*\
+\
+This document tells about using Large Objects and Visual Basic. All the main connection interfaces available in VB are discussed: DAO, ADO and RDO.\
+\
+Requirements to get the subroutines to work:
+
+- DAO, ADO and RDO interfaces available in VB
+- Created the lo type using the appropriate functions available in contrib/lo in the PostgreSQL source tree
+- Installed and properly configured the latest version of the PostgreSQL ODBC driver.
+
+In the example the database used has one table with only two fields. Here is the SQL definition:
+
+> ` CREATE TABLE MYTABLE(`\
+> `   MAIN INTEGER,`\
+> `   OBJECT LO`\
+> `); `
+
+The ODBC DSN I used in the example is named pgsql_test_blob. To insert a record, I suggest you to use the INSERT sql statement instead of the AddNew method (available in DAO, RDO and ADO). The AddNew method force you to declare a Recordset and this is bad because when you open it, VB creates a cursor and has to pass all the records in the table, slowing your application significantly.\
+\
+I think the examples are very simple and self explanatory. Some tips about which interface to use:
+
+- ADO and RDO are the best interfaces to connect to PostgreSQL. Personally, I think ADO is better only because it is new and actively supported by Microsoft. RDO is the old interface and it is not more developed.
+- DAO is very, very heavy and I suggest you not use it unless you are forced to do so.
+
+## DAO (Data Access Objects)
+
+> 
+>     Private Sub DAO_Connect()
+>         Dim chunk() As Byte
+>         Dim fd As Integer
+>         Dim flen As Long
+>         Dim ws As Workspace
+>         Dim cn As Database
+>         Dim rs As DAO.Recordset
+>         Dim strConnection As String
+>
+>         ' Initialize the DB Engine
+>         Set ws = DBEngine.Workspaces(0)
+>         Let strConnection = "ODBC;DSN=pgsql_test_blob;"
+>         Set cn = ws.OpenDatabase("", False, False, strConnection)
+>
+>         ' Open the table MYTABLE
+>         Set rs = cn.OpenRecordset("MYTABLE")
+>
+>         '
+>         ' Add a new record to the table
+>         '
+>         rs.AddNew
+>
+>
+>         rs!main = 100 '' a random integer value ''
+>
+>         fd = FreeFile
+>         Open "mydocument" For Binary Access Read As fd
+>         flen = LOF(fd)
+>         If flen = 0 Then
+>             Close
+>             MsgBox "Error while opening the file"
+>             End
+>         End If
+>
+>         ' Get the blob object into the chunk variable
+>         ReDim chunk(1 to flen)
+>         Get fd, , chunk()
+>
+>         ' Store it in the database
+>         rs!object.AppendChunk chunk()
+>
+>         ' Update changes
+>         rs.Update
+>
+>         ' Close the file
+>         Close fd
+>
+>         ' Close the record set
+>         rs.Close
+>
+>         '
+>         ' Read the blob object from the first record of MYTABLE
+>         '
+>         Set rs = Nothing
+>
+>         ' Open the table
+>         Set rs = cn.OpenRecordset("MYTABLE")
+>
+>         ' Open a file for writing
+>         fd = FreeFile
+>         Open "mydocument" For Binary Access Write As fd
+>         flen = rs!object.FieldSize
+>         ReDim chunk(1 to flen)
+>
+>         ' Get it from the database
+>         chunk() = rs!object.GetChunk(0, flen)
+>         ' ...and put it into the file
+>         Put fd, , chunk()
+>
+>         ' Close all...
+>         rs.Close
+>         Close fd
+>         cn.Close
+>         Close
+>     End Sub
+
+## ADO (ActiveX Data Objects)
+
+> 
+>     Private Sub ADO_Store()
+>         Dim cn As New ADODB.Connection
+>         Dim rs As ADODB.Recordset
+>         Dim cmd As ADODB.Command
+>         Dim chunk() As Byte
+>         Dim fd As Integer
+>         Dim flen As Long
+>         Dim main As ADODB.Parameter
+>         Dim object As ADODB.Parameter
+>
+>         ' Connect to the database using ODBC
+>         With cn
+>             .ConnectionString = "dsn=pgsql_test_blob;"
+>             .Open
+>             .CursorLocation = adUseClient
+>         End With
+>
+>         ' Here is an example if you want to issue a direct command to the database
+>         '
+>         'Set cmd = New ADODB.Command
+>         'With cmd
+>         '    .CommandText = "delete from MYTABLE"
+>         '    .ActiveConnection = cn
+>         '    .Execute
+>         'End With
+>         'Set cmd = Nothing
+>
+>         '
+>         ' Here is an example of how insert directly into the database without using
+>         ' a recordset and the AddNew method
+>         '
+>         Set cmd = New ADODB.Command
+>         cmd.ActiveConnection = cn
+>         cmd.CommandText = "insert into MYTABLE(main,object) values(?,?)"
+>         cmd.CommandType = adCmdText
+>
+>         ' The main parameter
+>         Set main = cmd.CreateParameter("main", adInteger, adParamInput)
+>         main.Value = 100 '' a random integer value ''
+>         cmd.Parameters.Append main
+>
+>         ' Open the file for reading
+>         fd = FreeFile
+>         Open "mydocument" For Binary Access Read As fd
+>         flen = LOF(fd)
+>         If flen = 0 Then
+>             Close
+>             MsgBox "Error while opening the file"
+>             End
+>         End If
+>
+>         ' The object parameter
+>         '
+>         ' The fourth parameter indicates the memory to allocate to store the object
+>         Set object = cmd.CreateParameter("object", _
+>                                              adLongVarBinary, _
+>                                              adParamInput, _
+>                                              flen + 100)
+>         ReDim chunk(1 to flen)
+>         Get fd, , chunk()
+>
+>         ' Insert the object into the parameter object
+>         object.AppendChunk chunk()
+>         cmd.Parameters.Append object
+>
+>         ' Now execute the command
+>         Set rs = cmd.Execute
+>
+>         ' ... and close all
+>         cn.Close
+>         Close
+>     End Sub
+>
+>     Private Sub ADO_Fetch()
+>         '
+>         ' Fetch the first record present in MYTABLE with a lo object stored
+>
+>         Dim cn As New ADODB.Connection
+>         Dim rs As ADODB.Recordset
+>         Dim fd As Integer
+>         Dim flen As Long
+>         Dim chunk() As Byte
+>
+>         ' Connect to the database using ODBC
+>         With cn
+>             .ConnectionString = "dsn=pgsql_test_blob;"
+>             .Open
+>             .CursorLocation = adUseClient
+>         End With
+>
+>         ' Open a recordset of the table
+>         Set rs = New ADODB.Recordset
+>         rs.Open "MYTABLE", cn, adOpenKeyset, adLockOptimistic, adCmdTable
+>
+>         ' Get the len of the stored object
+>         flen = rs!object.ActualSize
+>
+>         ' Initialize the file where to store the blob
+>         fd = FreeFile
+>         Open "mydocument" For Binary Access Write As fd
+>
+>         ReDim chunk(1 to flen)
+>
+>         ' Get it from the database
+>         chunk() = rs!object.GetChunk(flen)
+>         ' ... and store in the file
+>         Put fd, , chunk()
+>
+>
+>         Close
+>     End Sub
+
+## RDO (Remote Data Objects)
+
+> 
+>     Private Sub RDO_Store()
+>         Dim cn As New RDO.rdoConnection
+>         Dim rs As RDO.rdoResultset
+>         Dim cmd As RDO.rdoQuery
+>         Dim fd As Integer
+>         Dim flen As Long
+>         Dim chunk() As Byte
+>
+>         ' Connect to the database using ODBC
+>         With cn
+>             .Connect = "dsn=pgsql_test_blob;"
+>             .LoginTimeout = 3
+>             .CursorDriver = rdUseOdbc
+>             .EstablishConnection rdDriverNoPrompt, True
+>         End With
+>
+>         ' Create the INSERT statement to store the record in the database
+>         Set cmd = cn.CreateQuery("insert", _
+>                                      "insert into MYTABLE (main,object) values(?,?)")
+>
+>         ' Insert the first parameter
+>         cmd.rdoParameters(0).Value = 100 '' a random integer value ''
+>
+>         ' Open the file for reading
+>         fd = FreeFile
+>         Open "mydocument" For Binary Access Read As fd
+>         flen = LOF(fd)
+>         If flen = 0 Then
+>             Close
+>             MsgBox "errore in apertura file"
+>             End
+>         End If
+>
+>         ReDim chunk(1 To flen)
+>         ' Get it ...
+>         Get fd, , chunk()
+>         ' and store into the parameter object
+>         cmd.rdoParameters(1).Type = rdTypeLONGVARBINARY
+>         cmd.rdoParameters(1).AppendChunk chunk()
+>
+>         ' Finally execute the INSERT statement
+>         cmd.Execute
+>
+>         ' Close all
+>         Close
+>     End Sub
+>
+>     Private Sub RDO_Fetch()
+>         '
+>         ' Fetch the first record present in MYTABLE with a lo object stored
+>
+>         Dim cn As New RDO.rdoConnection
+>         Dim rs As RDO.rdoResultset
+>         Dim fd As Integer
+>         Dim flen As Long
+>         Dim chunk() As Byte
+>
+>         ' Connect to the database using ODBC
+>         With cn
+>             .Connect = "dsn=pgsql_test_blob;"
+>             .LoginTimeout = 3
+>             .CursorDriver = rdUseOdbc
+>             .EstablishConnection rdDriverNoPrompt, True
+>         End With
+>
+>         ' Open the table
+>         Set rs = cn.OpenResultset("select * from MYTABLE", rdOpenKeyset)
+>
+>         ' Get the length of the file
+>         flen = rs!object.ColumnSize
+>
+>         ' Initialize the file where to store the object
+>         fd = FreeFile
+>         Open "mydocument" For Binary Access Write As fd
+>
+>         ReDim chunk(1 To flen)
+>
+>         ' Get it from the database
+>         chunk() = rs!object.GetChunk(flen)
+>         Put fd, , chunk()
+>         Close
+>     End Sub
diff --git a/website/content/howto/visual-basic.md b/website/content/howto/visual-basic.md
new file mode 100644
index 00000000..17b96202
--- /dev/null
+++ b/website/content/howto/visual-basic.md
@@ -0,0 +1,103 @@
+---
+title: "Visual Basic"
+weight: 4
+aliases:
+  - /howto-vb.html
+---
+
+*Author: Dave Page (dpage@postgresql.org)\
+Release Date: 13 November 2001\
+Description: Example based Mini-Howto on Accessing PostgreSQL from Visual Basic*\
+\
+This document provides some sample code to get you started with Visual Basic & PostgreSQL.\
+\
+Requirements to get the subroutines to work:
+
+- Visual Basic 5/6
+- A reference in the VB project to Microsoft ActiveX Data Objects
+- A PostgreSQL datasource.
+
+The example code shown below may need some modification to make it actually work in your environment. There is one table used in the example:
+
+> ` CREATE TABLE vbtest(`\
+> `   id int4,`\
+> `   data text,`\
+> `   accessed timestamp`\
+> `); `
+
+## Code
+
+> 
+>
+>     Sub Main()
+>     Dim cn as New ADODB.Connection
+>     Dim rs as New ADODB.Recordset
+>      
+>       'Open the connection
+>       cn.Open "DSN=<MyDataSourceName>;" & _
+>               "UID=<MyUsername>;" & _
+>               "PWD=<MyPassword>;" & _
+>               "Database=<MyDatabaseName>"
+>      
+>       'Clear the table
+>       cn.Execute "DELETE FROM vbtest;"
+>       
+>       'For updateable recordsets we would typically open a Dynamic recordset.
+>       'Forward Only recordsets are much faster but can only scroll forward and 
+>       'are read only. Snapshot recordsets are read only, but scroll in both 
+>       'directions. 
+>       rs.Open "SELECT id, data, accessed FROM vbtest", cn, adOpenDynamic, adLockOptimistic
+>      
+>       'Loop though the recordset and print the results
+>       'We will also update the accessed column, but this time access it through 
+>       'the Fields collection. ISO-8601 formatted dates/times are the safest IMHO.
+>       While Not rs.EOF
+>         Debug.Print rs!id & ": " & rs!data
+>         rs.Fields("accessed") = Format(Now, "yyyy-MM-dd hh:mm:ss")
+>         rs.Update
+>         rs.MoveNext
+>       Wend
+>      
+>       'Add a new record to the recordset
+>       rs.AddNew
+>       rs!id = 76
+>       rs!data = 'More random data'
+>       rs!accessed = Format(Now, "yyyy-MM-dd hh:mm:ss")
+>       rs.Update
+>
+>       'Insert a new record into the table
+>       cn.Execute "INSERT INTO vbtest (id, data) VALUES (23, 'Some random data');"
+>
+>       'Refresh the recordset to get that last record...
+>       rs.Requery
+>
+>       'Get the record count
+>       rs.MoveLast
+>       rs.MoveFirst
+>       MsgBox rs.RecordCount & " Records are in the recordset!"
+>
+>       'Cleanup
+>       If rs.State <> adStateClosed Then rs.Close
+>       Set rs = Nothing
+>       If cn.State <> adStateClosed Then cn.Close
+>       Set cn = Nothing
+>     End Sub
+
+## Useful Functions
+
+> 
+>
+>     ' The escapeString function can be used to fix strings for us in INSERT and 
+>     ' UPDATE SQL statements. It will take a value, and return it ready for 
+>     ' use in your statement as NULL, or quoted with backslashes and single quotes
+>     ' escaped.
+>
+>     Function escapeString(vValue As Variant) As String
+>
+>       If IsNull(vValue) Then
+>         escapeString = "NULL"
+>       else
+>         escapeString = "'" & Replace(Replace(vValue, "", ""), "'", "''") & "'" 
+>       end if
+>
+>     End Function
diff --git a/website/go.mod b/website/go.mod
new file mode 100644
index 00000000..ae06dd1f
--- /dev/null
+++ b/website/go.mod
@@ -0,0 +1,5 @@
+module github.com/postgresql-interfaces/psqlodbc/website
+
+go 1.21
+
+require github.com/imfing/hextra v0.13.0 // indirect
diff --git a/website/go.sum b/website/go.sum
new file mode 100644
index 00000000..6557292b
--- /dev/null
+++ b/website/go.sum
@@ -0,0 +1,2 @@
+github.com/imfing/hextra v0.13.0 h1:1zhCYy0tA9ZRErFBlU6NJEgR1HjK69bgd52EmpwnG00=
+github.com/imfing/hextra v0.13.0/go.mod h1:vi+yhpq8YPp/aghvJlNKVnJKcPJ/VyAEcfC1BSV9ARo=
diff --git a/website/hugo.yaml b/website/hugo.yaml
new file mode 100644
index 00000000..60c88450
--- /dev/null
+++ b/website/hugo.yaml
@@ -0,0 +1,74 @@
+baseURL: https://odbc.postgresql.org/
+locale: en-us
+title: psqlODBC
+
+enableRobotsTXT: true
+enableGitInfo: false
+
+module:
+  imports:
+    - path: github.com/imfing/hextra
+  mounts:
+    - source: content
+      target: content
+    - source: static
+      target: static
+    # The release notes are kept once, in Changelog.md at the top of the
+    # repository.
+    - source: ../Changelog.md
+      target: content/changelog.md
+    # Files from docs/, which the installer and the source tarball also ship.
+    - source: ../docs
+      target: static/images
+      files:
+        - "*.jpg"
+    - source: ../docs
+      target: static/files
+      files:
+        - "*.reg"
+
+markup:
+  goldmark:
+    renderer:
+      # Some ported pages keep HTML tables and anchors.
+      unsafe: true
+  highlight:
+    noClasses: false
+
+menu:
+  main:
+    - name: Documentation
+      pageRef: /docs
+      weight: 1
+    - name: HOWTOs
+      pageRef: /howto
+      weight: 2
+    - name: FAQ
+      pageRef: /faq
+      weight: 3
+    - name: Changelog
+      pageRef: /changelog
+      weight: 4
+    - name: Search
+      weight: 5
+      params:
+        type: search
+    - name: GitHub
+      weight: 6
+      url: https://github.com/postgresql-interfaces/psqlodbc
+      params:
+        icon: github
+
+params:
+  description: The official PostgreSQL ODBC driver.
+  navbar:
+    displayTitle: true
+    displayLogo: false
+  footer:
+    displayCopyright: true
+    displayPoweredBy: false
+  editURL:
+    enable: true
+    base: https://github.com/postgresql-interfaces/psqlodbc/edit/main/website/content
+  page:
+    width: wide
diff --git a/website/layouts/_markup/render-heading.html b/website/layouts/_markup/render-heading.html
new file mode 100644
index 00000000..ebf58d5d
--- /dev/null
+++ b/website/layouts/_markup/render-heading.html
@@ -0,0 +1,14 @@
+{{- /* A level-1 heading that repeats the page title, such as the one at the top of
+     Changelog.md, is dropped because the layout already shows the title. Other
+     headings render as in Hextra. */ -}}
+{{- if and (eq .Level 1) (eq (.Text | plainify) .Page.Title) -}}
+{{- else -}}
+<h{{ .Level }} data-hextra-search-id="{{ .Anchor | safeURL }}" {{- with .Attributes.class }} class="{{ . }}" {{- end }}>
+  {{- .Text | safeHTML -}}
+  {{- if gt .Level 1 -}}
+    <span class="hx:absolute hx:-mt-20" id="{{ .Anchor | safeURL }}"></span>
+    <a href="#{{ .Anchor | safeURL }}" class="subheading-anchor" aria-label="{{ (T "permalinkLabel") | default "Permalink for this section" }}"></a>
+  {{- end -}}
+</h{{ .Level }}>
+{{- /* Drop trailing newlines */ -}}
+{{- end -}}
