using forms between fe and be dbs

[joebater]

Hi there

I've split my db into a front-end and back-end. I've password protected the backend and am using some forms locally (for maintanence etc) but would like to use some of the forms that exist with the front end (in order to generate queries etc).

1 ) Is this possible?
2) Can anyone suggest any references to learn more?

many thanks in advance
j.

 

[Fizzio]

What would be better is to create a separate maintenance Db. Try to minimise what is in the backend DB to minimise bloat and reduce the chance of corruption.
You can then link the maintenance Db to the backend data as you have with the FE but also import any forms/queries you may want to use in there. The bloat will then be in the maintenance Db, keeping the fe and be unscathed. HTH

 

[joebater]

Hi Fizzio

Thanks for your comments - sorry but I don't really understand that well.

The db that I have is to hold information about components purchased by the engineering company I work for. They issue a series of requirements documents (subject to quarterly revision, addition and removal). Consequently I've created tables for each set of requirements, and each set of responses (though the responses for many vendors obviously go into a single table - e.g.
for each record in the requirements table, there would be records for the part produced by company colour code red, colour code blue etc.) - yes the relations view is a nightmarish sight!

I've split the db into front and back in order to cater for a multiuser environment (as is usual). What might be slightly less usual (or maybe not) is that I don't want the users of the "fe" to be able to alter any information (hence the text box controls, not-in-list events for list/combo are all locked).

I've additionally written some forms for a "be" user (principally me but also people in my team if I were to go under a bus or whatever, throw my teddy bear out of the pram etc - not always a joke!), these include functionality such as automation with excel (the information that is added to the database is generally read from excel sheets so there is (nearly) a wizard-like interface for this), DAO to create tables and relations (for when new sets of requirements are to be added etc.)

It sounds like you're suggesting that I have the "be" consisting solely of tables (as is I guess traditional), and then have the "middle-end" ("me") to include this functionality (please correct me if I misunderstand), if so then in order not to replicate similar functionality again (e.g. generate and run a query) I remain with the same issue - code written in the "fe" needs to be accessed from the "me"... Perhaps one just has to import the forms into the the "me" also but it seems crazy to have forms and code doing something essentially the same in "several" db's. Is there now some way of saying "open the form 'frmGenerateQry' from db("fe")" even though the calling code is an event handler (say) from db("me")?

blue skies
j.

 

[Fizzio]

You have understood perfectly and that is a possible solution but as you say, you will have a lot of duplicated controls. An alternative would be to have a single fe with everything in it including 'administrator' functions but using access/custom security to limit access to these.

I have used both methods 'me' database (as you have eloquently termed) and using custom security to limit access. I would still consider leaving the be alone though for data storage only though (unless anyone here disagrees)

HTH