Access Database

@Grantmitch1 asked about using Microsoft Access for a website login and a points display. Using Access as a live web backend is possible on a Windows/IIS host with ODBC/ACE drivers, but it is fragile for public sites: file-based locking, limited concurrency, and many hosts (especially Linux) do not support the required drivers. @MidiMagic's suggestion to use PHP with a server-grade RDBMS is the usual, safer route.

A minimal, secure approach (for MySQL/MariaDB with PHP) is:

• Schema: users with id, username, password_hash, points.
• Store passwords with password_hash() and check with password_verify().
• Always use prepared statements (PDO or MySQLi) to avoid SQL injection.
• Manage sessions with session_start() and session_regenerate_id(true).
• For point changes use atomic SQL (no read-modify-write in PHP).

Example table and minimal login flow:

CREATE TABLE users (
id INT AUTO_INCREMENT PRIMARY KEY,
username VARCHAR(100) NOT NULL UNIQUE,
password_hash VARCHAR(255) NOT NULL,
points INT NOT NULL DEFAULT 0
);

<?php
// PDO example (assumes $pdo)
$stmt = $pdo->prepare('SELECT id,password_hash,points FROM users WHERE username = ?');
$stmt->execute([$username]);
$user = $stmt->fetch(PDO::FETCH_ASSOC);
if ($user && password_verify($password, $user['password_hash'])) {
session_start();
session_regenerate_id(true);
$_SESSION['user_id'] = $user['id'];
}
?>

To display or change points:

SELECT points FROM users WHERE id = ?;
UPDATE users SET points = points + 1 WHERE id = ?;

Practical notes: export Access tables to CSV and import into MySQL/phpMyAdmin when migrating; double-check date formats and autonumber fields. If Access must remain, use ODBC/PDO_ODBC on a Windows host, keep tight file permissions and frequent backups. Always run the site over HTTPS, avoid storing plaintext passwords, use prepared statements, and add rate-limiting and CSRF protections for login/forms.