It's easy enough to link to someone else's Excel spreadsheet and get their data into my Access database but I have to do it each month. They create a new tab each month (OCT-2007,NOV-2007,DEC-2007) for the month and the spreadsheets always have the same structure.
Is there anyway to tell my database to go out and look to see if the new spreadsheet has been created and if it has then import the data?
Need to get these into Access from an excel spreadsheet (located on sharepoint). I'm using the spreadsheet fields to create the table fields in Access.
What is the best way to accomplish this? I have a database that split into the Front end and the Back end. The form that the users entering the information uses the queries from two sources. One is the a table within Access and the other is an excel spreadsheet that I link to it. How can I update /replace the Excel spreadsheet while users are using the form of the front End?
I'm trying to clean up a form a bit and have it only show certain subforms/graphs if the data exists. I already have columns in a combobox query to show an "X" for if certain data appears:
Now, I know I could build another query and have some system go through and identify these things, but the easiest thing would be to reference the "X" in the columns of the combobox. Is there an easy way to reference values in the other (non-primary) columns? Or can you think of an easy way to make these subforms only be visible when the data exists? Maybe have an on load event for the subform?
Will Microsoft ever consider making another RAD program similar to Access that supports the .Net framework?
Just think of an IDE of a RAD program similar to Access that has a full set of toolbox items already built in .Net that supports all of the functions / options that Access currently supports in its forms, reporting etc. and have the ability to interface with all of the .Net database engines... :cool:
I have to fields in a form for a membership database that I want to relate to each other, 'date joined' and 'expires on'.
I have been trying to build an expression in the 'expires on' field that calculates the date which would be 12 months from the date entered in the 'date joined' field.
Can anyone please point me in the right direction.
first thing's first... i've never set up a Access db. I have, however, worked with php/mysql so I understand dbs and the basic principles behind them. i was hoping you could help me set up my db to accomplish my goals now and help me in the future when i want to make this system more advanced.
the purpose of the database is to track the 'stages' of several different projects as well as keep account of which contacts are involved.
example
I have projects A, B, C I have contacts I, II, III the stages of the projects are 1, 2, 3
I already have these tables (projects, contaces, stages)
the first issue is, i dont know how to assign mutltiple contacts for specific projects i.e. project A involves I, II, and III while project B only involves I and III. I would like a form to have a listbox with all the contacts in it and i could hold ctrl and select mutiple contacts for a specific project
the second issue... i would like to db to store dates of when a specific project moves from stage 1 to stage 2 for instance. i know i can set up fields in the projects table for these, but what happens when i add a new stage? will i need to go into the projects table and add a new field? can i make this dynamic?
i hope this makes sense to you. if you could give me direction, i would greatly appreciate it. before doing something that i will regret later, i hope you can give me some tips based on your experiences.
I have a table that holds the info on our fleet of company vehicles. One of the fields in the table is called ServiceDueDate. I want to be able to set up a query that shows any vehicles that have a service due in the next 30 days.
I know I'll need to use DLookup in there as well as Date - 30 but not sure exactly how to write the query.
I have a table of checking transactions. Some are past, some from today, and some are dated with future dates (such as recurring payments). Is there a way to set up a query that will exclude transactions that occur after upcoming paydays (1st and 15th) dynamically? For instance, if I have a transaction scheduled for the 2nd of next month (after payday on the 1st) I'd like to be able to separate it from the transactions that are coming out of this payday. Thanks for your help.
Can someone tell me how to calculate a future date in a bound field on a form? The form includes "date created", "life expectancy" and "review date" fields, all bound to the same table. I want the "review date" to be calculated by adding the "life expectancy" (number field, in days) to the "date created" field. I found some posts that were similar but none using bound fields.
Thanx so much for you help with this...I've spent quite a lot of time trying to come-up with a solution...to no avail.
I'd like to create a recordset from an Access database that reads the 'Date' field and only selects dates in the past. That way I can enter info ahead of time, give it a date of a week from now, and know it won't show up on my pages until next week.
It should be simple, but what I have isn't working. Here is my code:
Query = "SELECT Id, Date, Info FROM OldNews WHERE DateDiff('d', Date, date()) <= 365 ORDER BY Date DESC"
It lists all the records that are 365 days old, but it still shows any future dates as well.
I have a table of checking transactions. Some are past, some from today, and some are dated with future dates (such as recurring payments). Is there a way to set up a query that will exclude transactions that occur after upcoming paydays (1st and 15th) dynamically? For instance, if I have a transaction scheduled for the 2nd of next month (after payday on the 1st) I'd like to be able to separate it from the transactions that are coming out of this payday. Thanks for your help.
I've created a database to track my client information. I've split it into front end and back end databases. Everything there works fine so far.
I have other co-workers who track their own clients who I will be giving this database to. So we will soon have the same database with completely different data stored in them.
If I want to make changes in the future, I should easily be able to change the front end, get them a copy to install, and all should be well.
But what if I want to make changes to the backend? Like if I decide I want to track some completely new data in a separate table on the backend. I won't have the ability to just go out to the central server and change 1 backend database. There may be 10 identically structured backends on 10 different machines that all need the new table added to them, without effecting their unique data in the existing tables.
So, assuming my explaination made sense, is there a way to make backend changes like I'll need to? Or would I have to go to each backend database and manually make the changes?
I have a form for the user to enter new units which arrive in our warehouse, one field in DOM (Date of manufacture) which cannot be a date in the future obviously but could be todays' date. there is table level input mask to make the date 00/00/0000.i have this code on the form:
Private Sub dom_BeforeUpdate(Cancel As Integer) If Me.DOM > Date Then MsgBox "Please enter a Valid DOM", vbInformation, "Check again !!" Cancel = True End If End Sub
which doesn't accept any date whether it's today, last week, last year or in the future!
I've been hired to clean up and convert a flat filemaker database into access 2003 and I've spent the last two weeks learning the ins and outs of access and doing preparations. Well, today some high up database guy in another department told me not to use access because in the future when a new version of access comes out we will have to recreate the database from scratch because there are lots of problems converting between versions. I'm aware there might be some hiccups but I don't really agree with him. Plus once the database is up and functioning I don't see why we'd even have to upgrade it to a new version. It's just a small health centre patient database with info about patients and their treatments. Does anyone have any opinions about this. Thanks.
I'm designing a query that must calculate a future date based on a recorded date. Unfortunately it's not as simple as just using adddate (unless I was using Excel!). Here's my requirements:
Future Date = [StartDate] + 45 business days
I am able to take weekends into account, but haven't been able to figure out how to bring holidays into the equation. I have an existing holidays table that I am using for another query within the database (calculates # of business days between 2 existing dates).
Hope this makes sense... I've been staring at it all day so I may not be thinking clearly anymore.
Was wondering if it is possible to create a query or another method that would calculate future dates based on inputted info ?
For example a person inputs on a form a date completed (06/14/07) and then also selects a frequency of when this has to be revisited....monthly, quarterly, semi-annually.
So based on the date completed that the person inputs I'm trying to get the date if they select monthly of 7/14/07 (using above date example).
I am very new to Access and have virtually no experience with vb, I'm trying to build a customer database with some forms that enable myself and a couple of others to keep track of customer contact.I have designed my form with 5 buttons at the bottom of the page with different future date values, I have made a field in my database called FollowUpBy and i would like to be able to click the buttons and have access take today's date plus the relevant follow up time-scale and insert that into this field. Also but on a separate note, I have the yes/no box for follow up required is there a way to make the buttons at the bottom and the date picker unavailable (perhaps shaded or crossed out) unless this box is checked?
I trying trying capture the ID no. of a record for future use. I have tried different combinations on different form events. Nothing works, what am I doing wrong? The latest I have tried is the following, on the load event,
Code: Private Sub Form_Load() Dim LoadNo As String DoCmd.GoToControl "ID" LoadNo = Me.ID txtLoadNo = LoadNo End Sub
Any ideas on calculating future dates based on # of working hours. For example... If a task is suppossed to be completed in 32 business hours, when would that be? Considerations include standard working hours M-F, no working hours on weekend. I have to believe that someone has written this before and I don't need to reinvent the wheel. ANy help is much appreciated!
I am trying to find a simple way to determine the work date based on knowing the Start date and how many days ahead I want the date for. These means I need to exclude weekends and holidays.
I tried Pat Hartmans solution located at
[URL]
I discovered that the function in there that is supposed to do this does not account for weekends, only holidays.
I am very new to access and I am trying to figure out how to build an expression for one of my fields. I have a field called Order Date, which holds the date of when an order is filled. I then have another field called Fill By Date. This new field I want to be 2 weeks after the Order Date. Is there a way to auto fill this information so that when I enter a date into the Order Date, it will enter the date that is 2 weeks after into the Fill by Date?
I'm currently building my first database for a research project. When we enroll a participant, we need to have an enrollment date/time as well as an activation date/time (and they are not allowed to be the same because, rules). I was able to figure out how to auto-populate the current date/time when we've marked a person as enrolled. What I'm wondering is if it is also possible to auto-populate another field with the date/time, ten minutes in the future?