Upgrade To SQL Server - Forms To Be Based On Queries Rather Than Filters?
Oct 18, 2005
I am in the process of upgrading Access b/e to SQL b/e using .mdb and linked table as the front end ( as given as the best solution in many of the posts).
I remember reading in this forum ( Comment made by Pat Hartman) that forms should be based on queries rather than using a filter criteria.
I have a continuous form with project records. The user can double click one of the records to view further details of the project on a separate form. The code I have used to open the form is as follows:
Would this be a reduction in performance? Should the record source of the details form be changed to a query that has a where clause pointing to the selected record?
Thanks...Priya
We keep having our backend tables corrupt. We want to upgrade only the backend tables to SQL server. I don't even know where to start. What version of SQL server? I guess I find out if we have an existing licence in the company? Any help on this?
Is there an easy fast way to do this: We are having problems upgrading to SQL server for only our backend tables. The problem is we have SQL reserved words that can only be used by SQL Server. There is a huge list I was given. I assume this applies to all objects, in our ms access database. Any suggestions on how to at least 'find' all of these at once? Or fix this easily? I know which tables would not upload ...but in looking through them I don't even see which reserved word is causing the issue???
Also..our front end application with stay Ms access 2003. Do I still need to update any reserved words in that or just the tables?
I am trying to generate a report that is based off of a query. The query has a form filter that it needs to filter the data. I keep getting a jet engine error and couple others.
The form has year, start week, and end week on it. I can get the query to work fine. When I try to open the report, Access says it doesn't recognize the " [Forms]![frmUptimeFilter]![StartWeek] " as a valid field name or expression.
This works great to return a report if the user selects something from the combo box. How do I adapt this so that the user can also leave the combo box blank and filter the report to return all records?Additionally, what if I want to have the user filter between dates selected on the form; i.e. between 'txtStart' and 'txtEnd'
First of all I hope this question is relevant to this part of the forum, I thought this was the best place to put it, but my ignorance of the subject may mean it ends up being more closely related to one of the other areas.
I'm struggling with some statistical reporting on Email Enquiries, which I'm currently doing manually using Advanced Find in the Outlook Public Folders and putting counts into an Excel spreadsheet. I find the whole thing quite ackward (as you might imagine), and the Advanced Find in Outlook frustrates me as it can be quite limiting.
What I'd like to do is set up an Access Data Project as a front-end for the Exchange folders concerned. I'm pretty well versed in MDB's but I've never set up an ADP before. I assume this is possible as I'm under the impression that MS Exchange is basically an SQL Server database. Is this correct? Will I be able to configure it using the Wizard that appears when I create a new ADP (if given permission by the MS Exchange Admin)?
I have set up 2 tables, and got the tables linked with a foreign key. These tables store street names and house numbers.Ideally I would like to enter a street name, and then number from and number to, ie: Main Street, from 1 to 30.Each house number will has 4 fields associated to it.
The desired result in a form will be to enter the street name, numbers from and to, and then a sub form open up showing a list of numbers covering the range entered with 4 "Yes/No" fields next to each house number.Some streets could go up to as most as 300 houses, but I would not want that number shown for every street when it is not necessary. only the relevant number according to what is entered.All data would need to be stored and then queries and reports run against it.I am using access 2007 on windows 7.
The last two weeks I taught myself Access (and hurt quite a few braincells in the process) Yet I am getting close to what I want to achieve, but now I am stuck how to proceed with the following:
I want to have 'forms' view as my main interface for my records. This is working very nicely, and I like how I can scroll fast through all records with my mouse-wheel. I also need to be able to filter records that will be displayed and scrolled through this way, and I created a filter which I can now toggle on or off easily for this purpose.
But now my challenge is, I want to be able to quickly select different filters, so for example, show only forms with a certain date field content. Or filter only forms which have a certain check-box checked. Etc. etc. And later on probably a bit more advanced, like: display forms that both contain 'this' and 'that'.
But I can't find a way to create several different and selectable filters? So this should probably be achieved in quite a different manner?
I have a search form which suddenly stopped remembering filters between loads. I managed to accidentally replicate the behaviour on a second database where I knew the filters worked - in this case the code was
Code: Private Sub Form_Unload(Cancel As Integer) Me.Filter = "(False)" Me.FilterOn = True End Sub
Turns out that simply commenting out then uncommenting this section (while the form was open) was enough to break it. Filtering still works, but the form's filter property is forgotten when it unloads, and the only way to change it permanently is in Design View.
So I made a very simple test db with a filtered form, started faffing around with the code while it was open, and lo and behold the filters have stopped working. But I've compared the functional and non-functional versions and I can't for the life of me see what's been changed. I suspect I've run into some kind of bug (not that I should be fiddling with code while in form view anyway) but what can I do to revert it?
It turns out that I can force the filter to be saved by hitting Ctrl+S before I exit the form. Still no clue as to why v1 mysteriously works and v2 mysteriously doesn't. In the meantime, can I replicate Ctrl+S in VBA? I tried DoCmd.Save acForm "FormName", but no luck there.
I am creating a front end of a database that is the forms only version with ext. .accdr...I would like to create a way that each user of the front end can apply a filter using parameters, allowing the user to enter in their name when opening the front end.Form and Table name is "Non-Student Tasks Completed Daily" and "Student Connection Task" Field name is "SSC"..How can I get a box to appear when someone opens the database that askes them to enter their name to apply the filter?
I have a form with 5 options in a group. This works fine when I only have 1 filter applied to each button. I need to select the "Not Collected" button and have it filter out and show "Collected = No" and "Deleted = No". Here is my code..Case 3 is the one I'm currently working on. I can get the others once I figure out the first one.
Private Sub Frame799_Click() Select Case Frame799 Case 1
I'm having some issues using the cascading combo box technique on my form.
I have a form, which contains a subform in continuous view, which contains a few combo boxes.
One of those combo boxes (available resources) should be filtered depending on the value of 3 other combo boxes (task types, source languages, target languages).
What I would like to be able to do is run the filtering routine on this resources cbo (currently VBA code that changes the row source value) when the user clicks on it.
It's kind of working right now: when I click on the arrow to open up the drop down list, the values are indeed filtered. The problem I'm having though is that, if I then click on that same cbo for another record (or any other cbo in another record for that matter), the resource cbo of the record I previously set gets deleted.
I have been tasked to create a report menu for my users to select a report (there are about 20), select which filters that they want to apply to that report, then run based on what the user selected as the filters.
I have about 30 different filters to create, and based on which report the user selects, the filters that apply will need to be shown. I'm thinking the reports will be in an option group, and based on which report the users selects the filters that apply to that report will be displayed. From there the user can choose to apply a filter or not, and run the report.
I am trying to figure out the best way to tackle this. Should I try to create a table that contains the report name and type of filter to loop thru the controls to set visible, and build the SQL?
I have a number of forms that are bound to recordsets as follows:
Dim rs As New adodb.Recordset
sqlQuery = "Select * from myTable" rs.Open sqlQuery, sqlCNN, adOpenKeyset, adLockOptimistic Set Me.Recordset = rs Set rs = Nothing
In Access 2003, users could open these forms and filter on basically any field by using the right click-> Text Filters functionality.
In Access 2010, this functionality appears to work (users can apply the filter and the Toggle Filter button in the ribbon shows a filter is applied), but all of the records are still visible in the form.
Any work-around that does not involve redesigning the form to be non-recordset bound?
I am looking into re-creating something I have created in Microsoft Excel into Microsoft Access.What I do in the Excel spreadsheet, is when I type in an order number, various fields in the spreadsheet are populated using vlookups and ODBC's.
I wish to re-create this in Access but not sure how. I have a basic form, with various fields such as, order number, part number, description, quantity.What I have in my mind is that I would like to be able to type in an order number, then the rest of the fields would be populated by a query to a SQL Server database.i can see a way to do this using VBA but would rather look for a more direct way if possible.
Currently, I have 10 Users running a front end form that connect to back end data where they add to current records and eventually check that the record is complete.
I also have an "Apply Filter" button on the right hand side of the form that allows the user to apply filters to the records to show specific data that is not complete.
I am currently hearing that while the user is working, whether they apply filter or not, it seems as though all of a sudden, all of their completed work dissapears from their recordset hence not allowing them to go back to make changes to it if needed. I can only conclude that when a different user clicks apply filter, all users are affect some how... here are some examples of the code for the filter:
Code: Select Case [cboFilterValues] ' Where the user selects a filter parameter from a dropdown Case "All Data" strSQL = "SELECT * " & _ "FROM [Data Table] " & _ "WHERE [Complete] = No
Then it does:
Code: Me.RecordSource = strSQL
I am basically trying to find a way where only the user wanting to view the filter is affected... FYI, the other users arent actually seeing all the filters from the other user filter choice, they simply loose all their completed work from their form.
In a form I have a button which creates (in preview) an outlook message with a pdf report. It opens and displays just as I want it to, but if I chose to save that message in outlook and either send or cancel (i.e. allowing user to save to drafts and send later) then MS Access crashes.To ensure this wasn't to do with any compile / corruption within my full application I mirrored the process in a very simple 1 table / 1 form / 1 report db and still the same - access crashes after saving the outlook message and either sending the message or cancelling out the message.
Form code is as follows;Private Sub Command0_Click() On Error Resume Next DoCmd.SendObject acSendReport, "Table1", acFormatPDF, "someemaddress", , , , "REQUEST FOR INFORMATION" DoEvents On Error GoTo 0 End Sub
In my main application this process is embedded within a loop to send various filters of the report to different recipients, which works fine if 'save' is not used within Outlook..
I am having an issue trying to show all records when I load my form. It loads correctly when I don't have a record source for the main form. However, the combobox filters will not work. My goal is to have users be able to use the datasheet, subdatasheet and combobox filters. I can get the form to work just fine when I link the Main form and subform, but when the form opens it is filtered on the first record. I have been successful with this approach when using other forms, but they didn't require a subdatasheet.
Is there anyway I can have the comboboxes to filter yet be able to show all records until the user selects filters? Is this possible?I finally got my Manager to agree to use a database instead of Excel files based on this form setup and I need to make as "user friendly" as possible (look and function like a spreadsheet) I attached some pics of the form along with the code for the filter.
If you have a form that is based on a select query that has selected no records, the form will display as totally blank.
One way to avoid this is to ensure that the query is always able to select at lest one record; but Is there a way a message can be displayed if no records are selected?
Hi all, im using Access/Dreamweaver. Im decided to run the databse on queries this time - with no probs in ISS. As soon as i run it on the server i get this -
Microsoft JET Database Engine error '80040e37'
The Microsoft Jet database engine cannot find the input table or query 'search'. Make sure it exists and that its name is spelled correctly.
/search.asp, line 168
The database is fine. We have a dedicated server also. Any ideas what i may need to do to set it up on the server? thx
I have created several "pass through" queries in the last several years. However, Is it possible to run an SQL Procedure as a Pass Through Query. The procedure they want to run is set up to run a query, save the results to a server, and then run another query based on the saved data. I can get both queries to run as pass through queries, but I can't figure out how to save the data on the server. Is there a way to accomplish this? Can SQL procedures be run via Access?
My company is about to join the 21st century and they are upgrading from MS Office 97 to XP and Office 2003.
We have lots of Access databases, many designed by me, so if they don't work next Monday people will start comming to me for answers. As I am only familiar with Access 97 (and I am by no means an expert, even though everyone thinks I am!) are there any problems I can expect when we upgrade to the latest version?
