DataBase - Using Access 2003
Asked By Jennifer
20-Nov-09 02:31 PM
I have one table called customers and a table called orders. The primary Key
is CustomerID and the foriegn key is attached to Orders. I then created and
orders and customer forms. I want it so that when I have a Customer name on
the first form I only want orders from that customer to show up on the orders
form. I have tried creating a 1 to many relationship. That did not work for I
deleted. I did a insert a subdatasheet but it only saved that first
cumstomer's information. Please help? Jennifer
Windows XP
(1)
Access 2003
(1)
SubFormControl
(1)
MasterFields
(1)
LinkChild
(1)
AcXP
(1)
Integerity
(1)
Harddrive
(1)
ruralguy via AccessMonster.com replied to Jennifer
Jennifer,
Use a Form/SubForm arrangement and use queries of your tables rather than
directly to the tables. The LinkChild/MasterFields of the SubFormControl will
be the CustomerID.
--
RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
Please post back to this forum so all may benefit.
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200911/1
Tom van Stiphout replied to Jennifer
Hi Jennifer,
You may want to search your harddrive for Northwind.mdb; it has exactly the
same scenario you are speaking of. Dissect it, and you can learn quite a bit
on how to setup tables and their relationships, and then build forms on top
of that.
-Tom.
Microsoft Access MVP
KARL DEWEY replied to Jennifer
You need to create the 1 to many relationship between table called customers
and a table called orders with the primary Key CustomerID and the foriegn key
in Orders. Select options Referential Integerity and Cascade Update.
If you can not set the relations due to error it will be that you have one
or more records in the Orders table that does not have a matching CustomerID.
Run an 'unmatched' query to find and fix the records. Complete setting the
relationship.
Use a form/subform for customer/orders with Master/Child links with
CustomerID.
CustomerID does not need to be shown on the subform. As you add a new record
in the subform the CustomerID will automatically inserted in the Orders table.
Scrolling through the Customers in the main form you only see the orders
related to that Customer shown on the main.
--
Build a little, test a little.

Roger Jennings on Access / Sharepoint DataBase http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will be able to afford, because the pricing and licensing for the Enterprise version is very, very steep. The alternative is hosted Sharepoint / Access Services, and the costs do not seem terribly high. It seems to me that the pricing is upside-down. Big enterprises do not want to deploy Access apps in the browser - - they will build their own .NET apps, browser-based or not 2010, it could vastly increase those costs for organizations with legacy hardware). The features of Access 2010 used in conjunction with Sharepoint 2010 seem to me to be most compelling for and small businesses. I do not know if I could sell clients on hosted Sharepoint / Access. I have been able to sell clients on hosted Exchange, and it is been very W. Fenton http: / / www.dfenton.com / contact via website only http: / / www.dfenton.com / DFA / Access Discussions SQL Express (1) SQL Server (1) MySQL (1) Exchange Server (1) Windows Server (1
Access 2010 for software development DataBase Hi, What do I need to use Access 2010 (or perhaps 2007) to port our 2003 application and create an executable (MDE in Access 2003)? Are there any issues with 2010? -paulw Access Discussions SQL Server (1) SharePoint (1) Albert D. Kallal (1) Office 2007 (1) Office 2003 (1) Access 2007 (1) Access 2010 (1) Access 2003 (1) You can use Access 2010 to develop
Access 2010 with Sharepoint 2010 DataBase I found this article http: / / sharepointproconnections.com / Articles / tabid / 149 to me was these two points: client." Hopefully this means you can test out the Access 2010 in a browser capabilities. 2.0 AA compliance. Level 1 browsers, which support 100 percent functionality, include 32- bit versions of IE7, IE8, and Firefox on Windows. Level 2 browsers are IE7 and IE8 x64, Safari, Firefox on other platforms. Level 2 browsers will have some limitations in rendering and behavior." Bob Access Discussions SQL Server (1) MySQL (1) Visual Basic for Applications (1) SharePoint (1) Access 2007 (1) Access 2010 (1) Office 2003 (1) Windows 7 (1) Well, the question is do you really need to go to all that
2010: Essential Diffs? DataBase Sounds like Access 2010 is something of a different animal from preceding versions. Could anybody generalize the big issues? - - PeteCresswell Access Discussions SQL Server (1) Virtual PC (1) Windows XP (1) Visual Studio 2010 (1) SharePoint (1) Access 2010 (1) Office 2010 (1 Access 2007 (1) One starting point would be to browse Access team's blog. http: / / blogs.msdn.com / access / default.aspx Click on "2010 Intro Series" tag, which is high on the top of
Might be outgrowing Access but daunted by SQL Server DataBase I am close to completing the consolidation of various small Access databases and a couple of Excel spreadsheets that my little company uses (5 staff) into an all encompasing Access database and I was planning on splitting the database when I was finished to allow more and more obvious to me that I am going to need to give staff access to this new database from remote locations (outside of our office network). Two staff members out. It all started when I came across a very encouraging article on keeping your Access database as your front end application and linking to SQL Server database tables. I am more complicated than I had hoped. Can anyone suggest a simpler way of achieving remote access to my database? I have at my disposal a Network Storage Device which has remote access capabilities (this is where the database is currently stored), our website which it could be no IT guru by any stretch so please bare this in mind with any suggestions. Access Discussions SQL Server Migration Assistant (1) SQL Server 2005 (1) SQL Server 2008 (1) SQL