OOBC, Access, Postgres tlhowell[ at ]gmail.com 31.10.2005 22:49:33 Hello, I have a database application to be used in a multiuser environment. The Access file resides on 1 server and it contains forms, reports, queries, etc. The data resides on a Postgres server which Access links to using a system DSN. My question is, if I am not consistent in naming the DSN's the same way when I set things up on all the user's machines, will I run into problems? What do the experts recommend doing in this situation? How exactly does the ODBC driver resolve which DSN to use? Thanks, Tracy

Re: OOBC, Access, Postgres Philipp Stiefel <phil[ at ]codekabinett.de> 01.11.2005 13:58:05 tlhowell[ at ]gmail.com wrote: [Quoted Text] > I have a database application to be used in a multiuser environment. > The Access file resides on 1 server and it contains forms, reports, > queries, etc. You should rather use a separate copy of the frontend on every client machine. > The data resides on a Postgres server which Access links > to using a system DSN. My question is, if I am not consistent in naming > the DSN's the same way when I set things up on all the user's machines, > will I run into problems? Yes, of course! If the required DSN does not exist with the exact name on a client machine the app will not be able to establish a connection to you PostrgeSQL-Server. > What do the experts recommend doing in this > situation? You may link the tables without using any DSN at all. But you'll have to link the tables using VBA as the GUI does not support doing this. Instead of using the DSN=...-Syntax you'll have to supply all the information for ODBC-Connection in the Connect- Property of your tables. > How exactly does the ODBC driver resolve which DSN to use? It compares the names. Cheers Phil -- Access FAQs: http://www.mvps.org/faq/mvp_faq_links.htm#Access

Re: OOBC, Access, Postgres tlhowell[ at ]gmail.com 01.11.2005 17:49:52 Philipp, Thank you for your response. I have another question, which is, why do you recommend installing a seperate instance of the front end on each machine? Thanks, Tracy Philipp Stiefel wrote: [Quoted Text] > tlhowell[ at ]gmail.com wrote: > > > I have a database application to be used in a multiuser environment. > > The Access file resides on 1 server and it contains forms, reports, > > queries, etc. > > You should rather use a separate copy of the frontend on every > client machine. > > > The data resides on a Postgres server which Access links > > to using a system DSN. My question is, if I am not consistent in naming > > the DSN's the same way when I set things up on all the user's machines, > > will I run into problems? > > Yes, of course! If the required DSN does not exist with the exact > name on a client machine the app will not be able to establish a > connection to you PostrgeSQL-Server. > > > What do the experts recommend doing in this > > situation? > > You may link the tables without using any DSN at all. But you'll > have to link the tables using VBA as the GUI does not support > doing this. Instead of using the DSN=...-Syntax you'll have to > supply all the information for ODBC-Connection in the Connect- > Property of your tables. > > > How exactly does the ODBC driver resolve which DSN to use? > > It compares the names. > > Cheers > Phil > > -- > Access FAQs: http://www.mvps.org/faq/mvp_faq_links.htm#Access

Re: OOBC, Access, Postgres Philipp Stiefel <phil[ at ]codekabinett.de> 02.11.2005 10:39:47 tlhowell[ at ]gmail.com wrote: [Quoted Text] > Thank you for your response. I have another question, which is, why > do you recommend installing a seperate instance of the front end on > each machine? There are several reasons for this. The two main reasons are: - Corruption: It is much more likely that the frontend-MDB gets corrupted if several user are working with it at the same time. - Performance: It is faster to load forms and reports from a local MDB than from an MDB stored on a network drive. Take a look at Tony's website as well, he has published some information regarding this topic. http://www.granite.ab.ca/access/splitapp/index.htm Cheers Phil

Re: OOBC, Access, Postgres "Albert D.Kallal" <PleaseNOOOsPAMmkallal[ at ]msn.com> 18.11.2005 04:58:55 <tlhowell[ at ]gmail.com> wrote in message news:1130867392.910283.274970[ at ]g49g2000cwa.googlegroups.com... [Quoted Text] > Philipp, > Thank you for your response. I have another question, which is, why > do you recommend installing a seperate instance of the front end on > each machine? You can the following article of mine, and after reading it...there should be NO doubt as to why you split.... http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm You will get no stability if you don't give each user a copy of this application... -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal[ at ]msn.com http://www.members.shaw.ca/AlbertKallal