Search results

Well, the 2 table approach will work in any relational DB, not just access. But if u do want just 1 table with Tel, Tel2, etc. u may do just that by running a sub on the ordered data. The first thing, in either case, is to reorganize your data, removing the dups and blanks, and for that u'll...

Well, you will first have to organize the data correctly. Create 2 tables: tblStudent and tblStudentTel. tblStudent would have all the unique fields like StudentID, StudentName, StudentAddress, StudentDOB, etc... tblStudentTel would have just 2 fields: StudentID and StudentTel; combine these...

Well, u might save some tiny smiley images somewhere then load them in an image frame in your form (Single or Continuous view) Here would be a sample code to load the image: Sub getFileName() Dim fileName As String Dim result As Integer With...

How about: Select * FROM MyTable WHERE (MyDate BETWEEN [Date1] AND [Date2]) AND (MyTime BETWEEN [Time1] AND [Time2]); The names within the brackets refer to controls (textboxes, comboboxes, etc.) on the form where u would enter these parameters and display the filtered data. HTH

Is the Add New command behind a button? Try this code: Private Sub btnAddNew_Click DoCmd.Close DoCmd.OpenForm "frmName", , , , acFormAdd End Sub In order to be able to say something about your record moving err msg, u need to provide more info about the underlying data (tables, queries...

So u mean u have in ExistingColumn Item1, Item2 ... Item200, but u want to select just the interval Item31-Item40 and place that in NewColumn? Is NewColumn in the same table? If it is, on which line should the copied sequence start? on line 1 or line 31, and what happens to the remaining 170...

Well u can create a button and add the following code to it: Private SUb btnAdd_Click Dim db As DAO.Database Dim rs As DAO.Recordset Set db = CurrentDb() Set rs = db.OpenRecordset("Groups", dbOpenDynaset) rs.AddNew 'list all the fields of your table that u want to be added to, on the left...

Well, in order to create blueshirts2 after blueshirt1 has already been chosen, the value blueshirt1 has to be saved somewhere so the app can look it up then increment it. For one to be able to start thinking about some approach, u'll first have to make clear where u store these already chosen...

Well I'd suggest you start by throwing out your Fee table and delete "Annual Fee" in Customers: after all, if customer Jim has paid an annual fee of $50 in 2008, and in 2009 needs to pay $55, where would u store that second fee? Secondly you could create a new table FeeType, with 2 fields...

Try this: Open the vb editor, go to tools>references, look for Microsoft DAO 3.6 Library, select it. HTH

Ok, I assumed from the beginning that your tables are "normalized". It'd be helpful if you'd load some of 'em up here so I (and others) can take a look. If your tables are ok, then it's quite easy to generate a report with training due next month (or whenever, for that matter). Just add a...

Your DB design, i.e, the way your tables are structured and related is the very foundation of your app. If this is weak, the whole thing will be wobby and there ain't no VBA cure for that, that's

Well, like I suspected. Your db should be designed in such a way that these "cheeseholes" do not exist in your tables. If u give me some more to go on I can try to point you in the right direction. Regards.

First thing: do the fields MondayNurse, TuesDayNurse, etc. always contain data in every row, like for example: CaseNumber MondayNurse TuesdayNurse 1.................Joan.............Helen 2.................Frida.............Nancy Or does your table look more like: CaseNumber MondayNurse...

1. Create a report "rptShowTraining" designed to display the data u want to see/print. 2. Create a pop up form "frmShowTraining" with a combo that allows u to select the employee and 2 texboxes where the dates have to be entered. Create a button named "View" on the form and put this code...

Well I'm sure that almost anything can be done with data that has been saved following minimal normalization requirements. But to be able to help u out, one must have a rather clear idea about your data structure and about what u want to achieve. Means you have to elaborate more and be more...

Well, your subforms must be related to your main form thru some unique identifier, say TransactID. Select your subforms by clicking on the outer edge (the small square in the upper left corner should not have a selection mark in it), then right click for properties, then click the data tab to...

Try to requery the subform HTH

Well u can create a compound PK in a new table which combines RequestNumber and EmpoyeeID, then add the existing data to it thru an append query. This will thus identify each record by combining RequestNumber and EmployeeID and duplicate RequestNumbers will be allowed. Thing is that u have to...

Well I can't quite see how u would go about choosing either OrderID or SalesPerson in just 1 listbox. Do you have an option group with radio buttons or something like that? If I could make a suggestion I'd say it'd be much easier to create a combo "cboSalesPerson" with 2 columns: SalesPersonID...