This month’s featured course covers 16 hours of training in installation, management, and deployment of VMware vSphere virtualization environments. It's free for Premium Members, Team Accounts, and Qualified Experts!
Solved
MSAccess/VBA/DAO query result set not as expected
Posted on 2007-11-20
I have an application that I have to support that was written in MS-Access 2003 VBA with DAO access to ODBC PostgreSQL database tables.
The database was designed without the use of "no nulls" capability of PostgreSQL so a varchar field without valid data could be null, blank or space.
The db.OpenRecordset query is supposed to select all records where a particular varchar field (RecordType) is null, space or blank, but it is not selecting the null fields into the result set. Can anyone see what might be wrong with the code snippet or suggest an alternative to ensure that nulls are included in the result set?
Please don't suggest changing it to ADO. This system is in maintenance mode - I have better things to do with my time than rewriting old code. I just need the result set to be as expected.
The database was designed without the use of "no nulls" capability of PostgreSQL so a varchar field without valid data could be null, blank or space.
The db.OpenRecordset query is supposed to select all records where a particular varchar field (RecordType) is null, space or blank, but it is not selecting the null fields into the result set. Can anyone see what might be wrong with the code snippet or suggest an alternative to ensure that nulls are included in the result set?
Please don't suggest changing it to ADO. This system is in maintenance mode - I have better things to do with my time than rewriting old code. I just need the result set to be as expected.
Set db = CurrentDb
Set rs = db.OpenRecordset("select * from <tablename> where [supplier] = 'name' and ([RecordType] = null or [RecordType] = '' or [RecordType] = ' ') order by [Sys_ID]")
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
3 Comments
I'm not familiar with PostgreSQL so this is just a guess, but on most SQL databases that I've used if you want to check for a field being null you say
WHERE [FieldName] IS NULL
and not
WHERE [FieldName] = Null
Just a thought...
WHERE [FieldName] IS NULL
and not
WHERE [FieldName] = Null
Just a thought...
Active 5 days ago
Thanks. I didn't catch that.
IS NULL is proper for PostgreSQL - it uses standard SQL.
Sometimes it takes a second set of eyes... ;)
IS NULL is proper for PostgreSQL - it uses standard SQL.
Sometimes it takes a second set of eyes... ;)
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Traditionally, the method to display pictures in Access forms and reports is to first download them from URLs to a folder, record the path in a table and then let the form or report pull the pictures from that folder.
But why not let Windows retr…
It is possible to export the data of a SQL Table in SSMS and generate INSERT statements. It's neatly tucked away in the generate scripts option of a database.
In Microsoft Access, learn different ways of passing a string value within a string argument. Also learn what a “Type Mis-match” error is about.
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.
Suggested Courses
Course of the Month10 days, 23 hours left to enroll
718 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.