Which is better ' rs("fieldName") ' or ' rs!fieldName ' ?

[Brawn]

Which is better:

rs("fieldName")

or

rs!fieldName

[red]
Pros?
Cons?
[/red]
Any comments at all may be a help. Brawn

"My mind is my Shrine,
and my body the Temple around it."
-The difference between genius and stupidity is that genius has its limits-

 

[Foada]

Just my personal preference but I always use
rs("fieldName&quot as I think it makes the code easier to read as it more clearly shows the field name especially if you are not using the VB editor (no color) to view the code.
Just my opinion. Anything is possible, the problem is I only have one lifetime.

 

[bjd4jc]

The band operator is now technically out dated as I have read in a few places, so, I think it's best to use rs("fieldname&quot.

 

[IFELSETHEN]

If you are going to be programming in the .NET world you would want to start using rs.fields("FieldName&quot.

"Newer is not always better"

Regards

 

[chogben]

Rumour has it that rs!FieldName is quicker.

However, if you're going to upgrade to vb.net then you should consider using rs.fields("FieldName&quot.value.

Most likely, it's personal preference. However, I would say to pick one style and stick with it as long as possible...

 

[boflexson]

Technically, you should use:

rs.Fields.Items("FieldName&quot.Value

-My 2 cents -Adam T. Courtney
Stratagem, Inc.

http://www.Stratagemnet.com

 

[Francis]

I prefer !, it takes less typing
And
If you use ! then you can do
with rs
!Field1 = val1
!Field2 = val2
!Field3 = val3
end with

 

[SgtJarrow]

According to everything I have read, if you use

Me![whatever]

It is translated into

Me("whatever&quot at runtime


Therefore, you should use Me("whatever&quot when possible. Programming isn't a profession of choice.
It's a profession of calling...
"Hey Programmer, your application broke again!"

Robert L. Johnson III, A+, Network+, MCP
Access Developer/Programmer

 

[CasperTFG]

ALWAYS use rs("fieldName&quot.

Why...

If you use rs!fieldname and one of your fields is called Date, then rs!Date, will give an error. Or If you put a space in your field name like rs!field name, then that will also give an error.

I too began by using ! as it is less typing, but soon found so many errors that half my code had ! and the other half had Filed.("&quot. It was a big mess.

Craig, mailto:sander@cogeco.ca

Remember not to name the Lambs...
It only makes the chops harder to swallow

 

[Francis]

On the contrary, if it does get converted at run time then it makes no difference and so using the easiest thing to type is fine.
I have just done some quick tests, and ! appears to be marginally faster, but only a few percent, so it may not be.
Francis

http://www.controldraw.co.uk

 

[shmiller]

Craig,
First, you should NEVER have a field named "Date". Of course, sometimes it's already done and your stuck with it. Same goes for field names with spaces.
But you can just use brackets:
rs![Date]
rs![Batch Number]

I always use rs!FieldName. I find it easier to read and I like being able to use the With statement. It saves typing and is visually clear. Especially when you have more descriptive names for your recordset object and 10 or 20 fields.
But if the bang won't be used in the future, it might be a good idea to start writing it a compatible way now.

 

[vbvictim]

I like the rs!fieldname syntax much better. It is easier to read and can use with "with". Having said that, like most things in BG's world, it doesn't matter what I like! If .net likes the more difficult syntax, so be it. I doesn't matter that I have tons of existing code using the "!" notation.