Datasheets

[PhilOfWalton]

I am a firm hater of Datasheets, much preferring Continuous forms.

Can anyone tell me of when the use of a datasheet would be an advantage please.

Phil

[twinnyfo]

Hey Phil,

In general, I am in your same camp of Datasheet-hating. However, there are a few circumstances when I use them:

If I want to view a bunch of data and filter out particular sets of records, rather than going through all the trouble of building those filters thorugh VBA, I use a datasheet to quickly view the data I need. I also have the ability to lock various fields so I can "search" on certain fields, but prevent updates.

I also use datasheets if I have to import data from a spreadsheet (manual cut and paste required because there is not easy way to group and import susing VBA). This allows me to add many columns/rows at one time.

However, if I am jsut simply viewing data and updating individual records, I am a very firm believer of Continuous Forms.

Just my two cents.

[PhilOfWalton]

Certainly I had not thought of the copy & paste. That could be useful.

I suspect, though, that a number of our "Customers" use Datasheets instead of continuous forms as they don't know any better.

Phil

[twinnyfo]

Phil,

I suspect that this is the same reason they use split forms (or Navigation Forms, or any of the other "featuers" MS includes in MS Access).

Creating a functional, powerful DB using the basic tools is easier (in my opinion) than using these included features. I can envision the possibility of using certain features, but nothing really pops to mind.

The bottom line is: understanding your craft is more important than the bells and whistles that make it look pretty.

[PhilOfWalton]

Here's a change from normal:-

100% agreement.

Phil

[NeoPa]

TwinnyFo:
The bottom line is: understanding your craft is more important than the bells and whistles that make it look pretty.

I'll jump in here with a "Hear! Hear!". Very true indeed.

[zmbd]

Datasheets - yuck
I usually only use them when delving into the backend tables directly for troubleshooting and only need something quick and dirty that will disappear the moment I figure out the issue.

NavigationControl - AHHH these on the other hand I have a love/hate relationship with. I now have several front ends using this control and now that I have a decent understanding about how they work - they've grown on me and my end users actually like the interface - shrug.

[Seth Schrock]

I don't have as much experience as others, but I always use continuous forms because it seems like inevitably I need some After_Update code on one of the controls. So I just take the time at the beginning of the design instead of having to recreate the form later.