I have a form that deals with production data that has two combo boxes, one for the starting date and one for the finish date, as well as several radio buttons that give users the option to go back in week, month or quarter increments instead of going back to a specific start date.
Things were...
The mdb files I am trying to compact are out on the network, and are not a part of the application that is trying to do this. I have corrected the path names (previously they were pointing to the c: drive rather than the network) but I continue to get that error message. My boss said that she...
I have several buttons on a form that compact different parts of a database. When clicking on them, the program starts making constant error noises and the message bar at the bottom of the browser blinks different errors so fast that you cannot read them. Upon hitting control, alt, delete, I...
Is there a way to format the date so that it is easier to read? I have a feeling that my users will complain about 1-1-2003 and 21-31 2003 represented as 01012003_31122003.
Thanks for your help!
The programmer that was in charge of my database before me converted it from Access 97 to 2000. I believe part of the db is still in 97 format. Clicking on one of the buttons gives an error saying that the program cannot run visual basic code from within. This is a 97 problem.
How do I find...
Here's the code for the button that generates the snapshot.
Thanks!
Private Sub cmdSnapshot_Click()
Dim rsStartDate, rsEndDate As DAO.Recordset
Dim strSQL As String
Dim MyWorkDate As Date
Dim RptName As String
Dim dSQL As String
Dim RptPath As String
Dim RptPeriod As String
Dim...
I have a form that generates production reports from an access db. The form gives the user the option to generate reports in Microsoft Snapshot format, via the click of a button. When the user clicks this button, a Snapshot file is created and stored in a folder on the user's c: drive. I...
Would it be better to find which parts of the DB were not converted to Access 2000 and convert them? Supposedly, the code is already there to compact it, it's just having 97 troubles.
That seems to be compacting the db OK, but I keep getting an error saying that the old database could not be deleted and replaced by the new, compacted copy because it is read-only. It is not set to read-only in the properties list. Any ideas?
I am working on a database another programmer created. At some point the DB was converted from Access 97 to Access 2000. My boss has always felt that a few parts of the DB (mostly tables I think) did not get converted and are still in 97 format.
I am having some trouble with a compacting...
Do I put this code in the form that the user uses to run the report? Or should I make a report, put the code there, and have it create the spreadsheet? I really want to skip the report and go from the form straight to the spreadsheet.
Thanx
Normally, I'm not an excel user so my quesion may seem a bit easy. I have an excel spreadsheet that the user enters production information into. There are many ranges. The user wants the Totals to automatically populate a table, instead of her having to type in all the spreadsheet data, and...
It works fine as a query. Running it gives no problems. Total down and minutes down are separate, so removing or adding one shouldn't affect the other. I just can't figure this one out. Everything I see suggest that the subform should be working. :(
Does anyone know how to comment out SQL code when using an Access database? I know that you can use '/*' or '--' to comment out SQL on other types of databases, but not with Access.
I am having trouble getting the results of a select query to populate a text box in a subform. I can't figure out what I'm going wrong. The query deals with down production hours and is measured in military time. Part of the IIf statement in the select portion of the code is as follows...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.