front-end/back-end development question

[joyo]

I am new to front-end/back-end applications. I have a
little confusion about the development.

Should I write front-end and back end separately, or just
write one file, then use Database Splitter to split it to
front-end and back-end.

I think they both work, but which solution is better?

Thanks

joyo

 

[Andy Cole]

jojo

Whenever you start any project the first thing to be designed are the table
structures. If these are not right then everything else will be wrong.
Once you've got the table structure right, the 'Back-end' is complete. The
next stage is designing the Queries. Do these in a new db where you have
linked the tables in the back-end. The rest, forms, menus, reports, macros,
modules. are all 'front-end' things.

So, to answer your question, its just as easy (and IMO, better) to design a
split system as it is to design a single DB.

One caveat: If you are intending to use the MS Security model, start with
this so that your DB's are created under the security umbrella before any
objects (tables, forms etc) are added.

Apart from my very first DB in Access2, all my developments have been
designed as described above, even when the project is a single user system
as the 'back-end' is stored on a server and the User doesn't have to worry
about back-up (assuming IT services do their job!).

HTH

Andy

 

[Andy Cole]

jojo

Whenever you start any project the first thing to be designed are the table
structures. If these are not right then everything else will be wrong.
Once you've got the table structure right, the 'Back-end' is complete. The
next stage is designing the Queries. Do these in a new db where you have
linked the tables in the back-end. The rest, forms, menus, reports, macros,
modules. are all 'front-end' things.

So, to answer your question, its just as easy (and IMO, better) to design a
split system as it is to design a single DB.

One caveat: If you are intending to use the MS Security model, start with
this so that your DB's are created under the security umbrella before any
objects (tables, forms etc) are added.

Apart from my very first DB in Access2, all my developments have been
designed as described above, even when the project is a single user system
as the 'back-end' is stored on a server and the User doesn't have to worry
about back-up (assuming IT services do their job!).

HTH

Andy

 

[Allen Browne]

Good question. Naturally, there is no one right answer: it's a matter of
style

My personal preference is to start with a single MDB file, and split quite
late in the development process. I just find it simpler to work with a
single file: easier for any structural changes you need, even minor things
like correcting the misspelling of a field's Description. And of course
you're making a backup twice a day and keeping lots of copies, so it's
easier when these are just one file each.

BTW, I don't use the splitter. There are usually some tables I want in the
front end (such as postal code lookup tables, workstation preferences), so I
find it easier to just do the split manually.

 

[Allen Browne]

Good question. Naturally, there is no one right answer: it's a matter of
style

My personal preference is to start with a single MDB file, and split quite
late in the development process. I just find it simpler to work with a
single file: easier for any structural changes you need, even minor things
like correcting the misspelling of a field's Description. And of course
you're making a backup twice a day and keeping lots of copies, so it's
easier when these are just one file each.

BTW, I don't use the splitter. There are usually some tables I want in the
front end (such as postal code lookup tables, workstation preferences), so I
find it easier to just do the split manually.