At first glance, the 'ON DELETE SET NULL' option in SQL Server 2005 may not seem like a big deal, but once you've seen how it can be used, I think you will be impressed. The basics? If Order.CustomerID has a foreign key to Customer.CustomerID and a customer is deleted, 'ON DELETE SET NULL' causes the CustomerID field in each of that customer's orders to be set to NULL.
2005-02-26
946 reads
Learn how to bind a form dynamically to a recordset created from an XML file. This simple application can be the starting point for a powerful solution for your customers and should be considered a part of your arsenal when developing Access application.
2005-02-25
1,724 reads
Try the following suggestions as originally suggested by Frank Miller of Microsoft PSS and extensively updated by me. Almost all of these tips also apply to Microsoft Access 97.
2005-02-25
2,238 reads
For some years, I have been asked to review a product that I have only just gotten around to looking at. It was developed by Garry Robinson, who publishes a very useful web resource called vb123.com and who recently wrote one of the best books on Access security, Real World Microsoft Access Database Protection and Security. The product is called The Access Workbench (TAW)
2005-02-25
2,359 reads
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
2005-02-24
1,438 reads
Jon Sigler of Microsoft visited the Denver Access users group with some comments about where Access is going.
2005-02-24
3,281 reads
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:
2005-02-23
3,934 reads
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.
2005-02-23
1,852 reads
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
2005-02-22
1,795 reads
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.
2005-02-22
1,094 reads
By Kevin3NF
IT leaders have a lot on their plates! Budgets, staffing, security, uptime, and keeping...
Want to really level up your SQL game? I mean, go from good to great? This March...
By Steve Jones
We published an article recently at SQL Server Central on Tally Tables in Fabric...
Comments posted to this topic are about the item Dynamic T-SQL Script Parameterization Using...
Buy Netherlands Driver’s License Online, looking to buy a Netherlands driver’s license quickly and legally? At...
Comments posted to this topic are about the item Multiple Sequences
In SQL Server 2022, I run this code:
CREATE SEQUENCE myseqtest START WITH 1 INCREMENT BY 1; GO CREATE TABLE NewMonthSales (SaleID INT , SecondID int , saleyear INT , salemonth TINYINT , currSales NUMERIC(10, 2)); GO INSERT dbo.NewMonthSales (SaleID, SecondID, saleyear, salemonth, currSales) SELECT NEXT VALUE FOR myseqtest , NEXT VALUE FOR myseqtest , ms.saleyear , ms.salemonth , ms.currMonthSales FROM dbo.MonthSales AS ms; GO SELECT * FROM dbo.NewMonthSales AS nmsAssume the dbo.MonthSales table exists. If I run this, what happens? See possible answers