Visual basic and emprt fields

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

tjj - 29 May 2007 17:16 GMT

I recently converted from Access 97 to 2003. (we're a little behind the
times at my company). Anyway, we have some visual basic code which
interfaces with the Access database in order to populate BOM's in AutoCAD,
etc.

My problem is that the code does not like fields with 'null' values. It
didn't seam to mind then in 97? I've since entered a meaningless character
in those fields to get the code to function so the company can still run, but
is there a 'real' fix?

I'm only self taught at VB, but I think it has something to do with an empty
recordset.

Reply to this Message

Douglas J. Steele - 29 May 2007 17:19 GMT

Without more details of what your code is doing, it's practically impossible
to comment.

If you're trying to pass values from your recordset to variables, be aware
that the only variable type that can contain Null values is the Variant data
type. You either need to ensure that your variable is a Variant, or else use
the Nz() function to convert the Null to a value that the variable can hold.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

>I recently converted from Access 97 to 2003. (we're a little behind the
> times at my company). Anyway, we have some visual basic code which
[quoted text clipped - 11 lines]
> empty
> recordset.

Reply to this Message

Baz - 29 May 2007 17:22 GMT

Please post the code.

> I recently converted from Access 97 to 2003. (we're a little behind the
> times at my company). Anyway, we have some visual basic code which
[quoted text clipped - 8 lines]
> I'm only self taught at VB, but I think it has something to do with an empty
> recordset.

Reply to this Message