Access to SQL "Bill" <bill[ at ]bill.com> 04.07.2006 19:07:40 Hi All, Forgive my ignorance here and if this is the wrong forum then apologies and can you advise where it should go please. I am a mere mortal who has developed an Access 2003 shared database that has outgrown its original single use brief and is now in use across the organisation. We recently had a corruption that required some work getting the database back and we now want to transfer to the correct IT support team for improved resilience and ongoing development and maintenance. They have both Oracle and SQL Server and while I appreciate that this is perhaps not the forum to get an unbiased view ;-) can anyone give me, or direct me to advice on what we should be using please. Also for my benefit would the application still run through Access for the front end forms and SQL for the backend database? Thanks for any help. Bill

Re: Access to SQL "David Portas" <REMOVE_BEFORE_REPLYING_dportas[ at ]acm.org> 04.07.2006 20:26:14 Bill wrote: [Quoted Text] > Hi All, > > Forgive my ignorance here and if this is the wrong forum then apologies and > can you advise where it should go please. > > I am a mere mortal who has developed an Access 2003 shared database that has > outgrown its original single use brief and is now in use across the > organisation. We recently had a corruption that required some work getting > the database back and we now want to transfer to the correct IT support team > for improved resilience and ongoing development and maintenance. They have > both Oracle and SQL Server and while I appreciate that this is perhaps not > the forum to get an unbiased view ;-) can anyone give me, or direct me to > advice on what we should be using please. > > Also for my benefit would the application still run through Access for the > front end forms and SQL for the backend database? > > Thanks for any help. > Bill Access can act as a front end for SQL Server, Oracle or any other database that supports an OLEDB provider. I can't tell you whether to use SQL Server or Oracle because I don't know your business, your requirements or your IT environment. In principle, those who run IT / IS for your business should be best-placed to make that decision. If they are going to develop the new database then best listen to their advice first. What do they say? -- David Portas, SQL Server MVP Whenever possible please post enough code to reproduce your problem. Including CREATE TABLE and INSERT statements usually helps. State what version of SQL Server you are using and specify the content of any error messages. SQL Server Books Online: http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx --

Re: Access to SQL "Bill" <bill[ at ]bill.com> 04.07.2006 21:24:06 [Quoted Text] > > Access can act as a front end for SQL Server, Oracle or any other > database that supports an OLEDB provider. > > I can't tell you whether to use SQL Server or Oracle because I don't > know your business, your requirements or your IT environment. In > principle, those who run IT / IS for your business should be > best-placed to make that decision. If they are going to develop the new > database then best listen to their advice first. What do they say? > > -- > David Portas, SQL Server MVP > > Whenever possible please post enough code to reproduce your problem. > Including CREATE TABLE and INSERT statements usually helps. > State what version of SQL Server you are using and specify the content > of any error messages. > > SQL Server Books Online: > http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx > -- > David, Trouble is I suspect the advice from IT has a pro Oracle bias!!! Regards. Bill

Re: Access to SQL "David Portas" <REMOVE_BEFORE_REPLYING_dportas[ at ]acm.org> 04.07.2006 22:22:23 Bill wrote: [Quoted Text] > David, > > Trouble is I suspect the advice from IT has a pro Oracle bias!!! > > Regards. > Bill If IT will be responsible for developing and supporting the system then what should matter to you is their ability to deliver a service, not whether their opinion is biased or not. If your IT department has a big investment in a particular DBMS and if their skills base is mostly centred on that DBMS then probably that IS the platform on which they can provide the best service to you as an IT customer. The real problem seems to be that you don't trust your IT department. That's not something we can solve in this newsgroup. If you want to compare the features of SQL Server and Oracle in general then take a look at: http://www.microsoft.com/sql/default.mspx http://www.oracle.com/database/index.html -- David Portas, SQL Server MVP Whenever possible please post enough code to reproduce your problem. Including CREATE TABLE and INSERT statements usually helps. State what version of SQL Server you are using and specify the content of any error messages. SQL Server Books Online: http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx --

Re: Access to SQL "Gil Lapid Shafriri" <gilsh[ at ]microsoft.com> 08.07.2006 07:36:56 It is my understanding that ADP project can work only against SQL Server and not against any general OLEDB provider. If you want Access to work against non SQL Server database you have to choose the linked table approach and not an ADP project. There are plus and minuses to each approach but if you like ADP then you can try to make the case for using SQL Server. Gil Lapid Shafriri Program Manager SQL Server Migration Assistant Microsoft http://www.microsoft.com/sql/solutions/migration/default.mspx "David Portas" <REMOVE_BEFORE_REPLYING_dportas[ at ]acm.org> wrote in message news:1152051742.996970.267690[ at ]75g2000cwc.googlegroups.com... [Quoted Text] > Bill wrote: >> David, >> >> Trouble is I suspect the advice from IT has a pro Oracle bias!!! >> >> Regards. >> Bill > > If IT will be responsible for developing and supporting the system then > what should matter to you is their ability to deliver a service, not > whether their opinion is biased or not. If your IT department has a big > investment in a particular DBMS and if their skills base is mostly > centred on that DBMS then probably that IS the platform on which they > can provide the best service to you as an IT customer. The real problem > seems to be that you don't trust your IT department. That's not > something we can solve in this newsgroup. > > If you want to compare the features of SQL Server and Oracle in general > then take a look at: > > http://www.microsoft.com/sql/default.mspx > http://www.oracle.com/database/index.html > > -- > David Portas, SQL Server MVP > > Whenever possible please post enough code to reproduce your problem. > Including CREATE TABLE and INSERT statements usually helps. > State what version of SQL Server you are using and specify the content > of any error messages. > > SQL Server Books Online: > http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx > -- >

test computer network "Long Truong" <longtruong78[ at ]hotmail.com> 12.07.2006 07:34:10 testing mail back toyou "Bill" <bill[ at ]bill.com> wrote in message news:O2Hqi05nGHA.3348[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > Hi All, > > Forgive my ignorance here and if this is the wrong forum then apologies and > can you advise where it should go please. > > I am a mere mortal who has developed an Access 2003 shared database that has > outgrown its original single use brief and is now in use across the > organisation. We recently had a corruption that required some work getting > the database back and we now want to transfer to the correct IT support team > for improved resilience and ongoing development and maintenance. They have > both Oracle and SQL Server and while I appreciate that this is perhaps not > the forum to get an unbiased view ;-) can anyone give me, or direct me to > advice on what we should be using please. > > Also for my benefit would the application still run through Access for the > front end forms and SQL for the backend database? > > Thanks for any help. > Bill > >