Connecting a second 'front end' to a DSN

I

Isis

I have a client who has some predictive dialling software - this has an
access database at it's heart - they have developed a 'front end' access
database that they use for various things - I would like to implement a
few forms and queries for a certain part of the business to use but I
don't want to mess with their front end so....

I thought I would just create my own small front end and connect it to
the same db that their front end connects to. They are already running
multi user for their front end and I presume that as the db actually
belongs to this predictive dialling software, that is also being used
multi user. Is there any reason not to do what I have in mind ? It would
also mean that I could make changes to my front end while their users
carry on using their db - this makes the maintenance and developement of
my db much more viable.

Any thoughts or pointers would be really welcome - How do I create the
ling to the existing DSN.

Thanks for any help.

Regards
 
A

Arvin Meyer [MVP]

I have had as many as 15 different front-end database applications connected
to a single set of data tables on a back-end on the server. What you need to
be careful of is that you do not violate any of their form validations, and
that they have enforced referential integrity, so that you do not mess up
their data.
 
M

mcnews

I have a client who has some predictive dialling software - this has an
access database at it's heart - they have developed a 'front end' access
database that they use for various things - I would like to implement a
few forms and queries for a certain part of the business to use but I
don't want to mess with their front end so....

I thought I would just create my own small front end and connect it to
the same db that their front end connects to. They are already running
multi user for their front end and I presume that as the db actually
belongs to this predictive dialling software, that is also being used
multi user. Is there any reason not to do what I have in mind ? It would
also mean that I could make changes to my front end while their users
carry on using their db - this makes the maintenance and developement of
my db much more viable.

Any thoughts or pointers would be really welcome - How do I create the
ling to the existing DSN.

Thanks for any help.

make sure the DSN exists on the PC that your client lives on and
simply link to the source via ODBC.
 
I

Isis

(e-mail address removed):

Thanks to both of you for your replies - I am not actually intending to
allow any updates - I just want to export some of the data to a csv file -
at the moment they export the data to a spreadsheet - convert it to a csv -
reformat the data and then save it to a file (csv) for a label printer to
print from - I have automated the excel part of the buainess but then
thought why not do all this direct from the db to the csv - the code I have
written is vb (code in an excel spreadsheet) so I am assuming that I will
be able to get it working in access.

The DSN is on the machine I will use to get at the Tables.

Thanks
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top