SQL Server 2000 and Access databases are two technologies closely linked with the new Access ADP format using SQL Server as the basis for the code. Access Projects are also a way to closely link the two products together and take advantage of each to produce an application very easily. Author Kathi Kellenberger brings us part 3 of her Access series with a look at Access Projects.
Recently, SwisSQL approached me for a review of their product that can convert SQL statements from one dialect to another. They told me that "SwisSQL SQLOne Console" is a GUI application that can convert SQL statements from one RDBMS implementation to another and the dialects supported include:
Microsoft SQL Server
Sybase
Oracle
IBM DB2
Informix
MySQL
PostgreSQL
MySQL
and last but not the least, ANSI SQL
Jon Sigler of Microsoft visited the Denver Access users group with some comments about where Access is going.
Microsoft Access targets individual information workers and small teams that use the Microsoft Office System to track, manage, prioritize, and act upon an increasing volume of business information. The data stored in these databases rarely justifies moving to a more robust platform until the application begins expanding into departmental scenarios. When this happens, it is worthwhile to consider moving the data into a more robust platform for enhanced reliability, scalability, and greater IT control. In most cases, the data can be moved through a process called "upsizing" while the Access application front-end continues to provide information workers with access to critical data. Microsoft has created resources in the following three categories to help manage Access data in your organizations:
Create a PowerPoint slide presentation from scratch using Access data. In addition, display and control a slide show from within an Access form. Walk through the solution and explore ways to extend the sample for your own applications.
Online Chat with Chat Participants: Tim Getsch, Microsoft Access Program Manager, JP Bagel, Site Manager, Mike Wachal, Lead Beta Engineer, Mike Gunderloy, independent Access developer, Sanjay Jacob, Microsoft Access Program Manager, and Rita Nikas, Microsoft Access MVP Lead
Jan Fransen reviews how to use the Microsoft Office Access 2003 Runtime with the Microsoft Access 2003 Developer Extensions so users without Microsoft Access 2003 installed can still use Access-based applications.
If you are really interested in the fastest performance, don't use Access as a front-end to a SQL Server database. While Access is relatively easy to learn and fast to develop in, its performance if poor when compared to other front-end options. But if you like to develop in Access, or don't have any choice, then the tips on this page will help a little to boost your application's performance.
The central place for Australia's SQL Server User groups and a list of their meeting times is now available.
SQL Server and Access are usually linked together as Access used for applications at the beginning of their lifecycle that are later moved to SQL Server when the load gets too high or the data sizes grow. There are often cases where you may also want to use SQL Server as a backend to an Access application. But how do you get your data from Access to SQL Server? Author Dinesh Asanka brings us an overview of the various ways that you can move your Access database to SQL Server.
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi all, I just started using VS Code to work with DB projects. I...
Comments posted to this topic are about the item Fun with JSON II
Comments posted to this topic are about the item Changing Data Types
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers