Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
Password Reminder
Register
Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old February 15th, 2007, 11:15 AM
Friend of Wrox
 
Join Date: Sep 2005
Location: , , USA.
Posts: 106
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Yahoo to Corey
Default Oracle back-end MS-Access 2003 client front-end

Hello everyone. The company I’m working for is looking to convert my MS database into a Oracle database.
Can anyone tell me the advantages and disadvantages of a Oracle back-end with a MS-Access 2003 client front-end

Thanks

Corey


Reply With Quote
  #2 (permalink)  
Old February 15th, 2007, 03:42 PM
Friend of Wrox
 
Join Date: Jan 2007
Location: , , .
Posts: 109
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via AIM to scandalous Send a message via MSN to scandalous
Default

Corey,

I have a very limited knowledgebase to give effective advise on the subject but here is what my thought is.

Using the backend as oracle will allow more traffic (Simultaneous users) and a larger recordset (more than 50MB or what ever the suggested Access DB size is) to be stored. I would think of it like upsizing it to SQL Server. My company is doing the samething with what I am making but they want it on thier intranet. Using MS Access is as a front end is logical because implementation is easy to use and manipulate data.
Well thats as much as i can tell you LOL.

Reply With Quote
  #3 (permalink)  
Old February 16th, 2007, 08:31 AM
Friend of Wrox
Points: 9,611, Level: 42
Points: 9,611, Level: 42 Points: 9,611, Level: 42 Points: 9,611, Level: 42
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Mar 2004
Location: Washington, DC, USA.
Posts: 3,069
Thanks: 0
Thanked 10 Times in 10 Posts
Default

You should be able to use Oracle as a back end, but you will probably want to use a DSN to connect to it. This is a little slower than provider statements, but probably safer since DSN's are essentially a service and Access doesn't care what is on the other end.

You will also want to make sure that your data types are correctly aligned between the Access front end and Oracle tables.

Are you using local tables with datasets from Oracle, or linked tables?

mmcdonal
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Front end Vs Back end ricmar Access VBA 3 May 27th, 2008 02:36 PM
Ms Access front End with Oracle 10g Back End rahul123 Oracle 1 July 9th, 2007 01:03 AM
Oracle Back End - MS Access Front End - Multi User ckaliveas Oracle 1 February 1st, 2007 06:00 AM
Re-linking the front and back end Scripts82 Access VBA 2 February 24th, 2006 12:26 AM
using msde and sqlserver with access front-end catkins Pro VB 6 1 April 1st, 2004 04:00 AM



All times are GMT -4. The time now is 12:03 AM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.