To Bound or Not 3

[GulfImages]

Hello All,

I've been using access since way back in v1, I'm not a programmer but I have written several applications for different companies that have worked well for many years. My best efforts have been using unbound forms and code to update, edit and save records. With bound forms there always seems to be a way to get around validation issues such as forcing certain fields to be filled etc...

The ones where I have used bound forms and the access features have given me the most problems, people just have problems with the way data is saved automatically and such. They just want a form that is either blank and ready for a new record, to pull up records and edit them and then save them. ike in other progams. With unbound forms I have a new button, a save button and a find button, works great but is a pain to code for validation and changes and to deal with subforms.

I asked here once and was told by several that the unbound form is the way to go but I'm just really tired of all the extra coding that goes with it. I've seen some comments lately that most developers use bounds forms and such.

Does anyone have any general comments or directions they think I should look into? I'm not looking for details, just some general info from others on these issues. Any example projects that I can download and examine would be great. I'm working on something for my own business and I want to be happy with it.

Am I trying to have my cake and eat it too?

Thanks,
Bobby

 

[JoeAtWork]

The pros to automatic binding is that it is so much quicker to develop in. I find the key to using it successfully is you have to follow the "Access way" of validating, saving (i.e. move off the record), reporting errors (i.e. basically report as they happen), etc.

If you have very complex validation rules, then binding probably won't work. In such a case, I usually write the application in VB6 (an easier and stabler environment than Access, in my opinion).

 

[alvechurchdata]

Am I trying to have my cake and eat it too?

I think you are, it's the bound forms that give Access much of its development speed.

I don't go as far as JoeAtWork though, I still stick with Access even if I do have to write a lot of DAO code. I'll agree that the mechanics of development are better in VB but some things that are easy in Access become much more difficult - things like reports, exporting to Excel or sending an email.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[Ed2020]

GulfImages,

Whilst it is probably true that most developers use bound forms I suspect it tends to be the less experienced/novice developers who stick to bound forms (no offense meant to those who do - this isn't necessarily always the case).

I always use unbound forms as I much prefer the extra level of control it gives me over retrieval/validation/saving of data. It is true that this involves a lot more work initially though.

One of my prefered methods is to create a class around the forms data source (be it a table, query, etc) which encapsulates all the filtering, searching, adding, amending and validation routines into one object. Although this initially requires even more coding than unbound forms usually do I find it makes life easier in the long run.

Ed Metcalfe.

Please do not feed the trolls.....

 

[GulfImages]

Thanks everyone for your advice, these are just the kind of opinions I'm looking for.