Hi All,
We're currently rolling out 2003 Runtime and I've had a few users requesting multiple open seesions of the same database. I thought sure no problem, and then found that it doesn't look like it's possible with Runtime.
Can anyone confirm whether there is a way around this?
It's just that they all had full version of 97 before and now were limiting them all to Runtime! :D
We are considering rolling out a number of access reports to users within our organisation who currently do not have access installed, nor do we want them to. Run time seems the obvious route. I see the runtime module is included in Access 2003 but I cant see if you have to install Access on the users PC in a "Runtime mode only" way or if the Developer tools have to be purchased to get the package wizard so you can send the package out with run time. Basically we want users to be able to access the database from the server but we do not want them to have the ability to do any thing else in access . i know read only rights will enable that to be done in the particular database but we don't want them building their own db's and the bothering IT when they come across something difficult....
Am using the standard files ACCESSRT.MSI and ACCESSRT.CAB to install Runtime.
Does anybody know a QUICK way of supressing the annoying security messages which pop up, when the application starts under this configuration?
I don't want to write any fancy install wizards or scripts, just need a basic runtime install like the above method, but with "Low" Macro security set.
I have developed an application and packed it into a runtime version. However, in the runtime version the shortcut menus do not work. The reason why I want the user to have that possibility is that the application has two hyperlink fields and it is much easier for the users to be able to browse to the documents instead of typing each link with all the errors that might give as well. Any help would be appreciated.
Our company recently switched over to a Microsoft 2003 server and I noticed in our database, before several employees could work in our access database. Now only 1 person at a time can enter the database. I splited the database and added shortcuts of the front end on each individual's desk but again only 1 person at a time can make entries. We all share a M drive. How do I fix it so we all can work in the database at the same time?
Before the upgrade, we had the 2000 server and everything worked fine w/ the access database; we all could work in the database; however, w/ the new 2003 server we are having problems as I explained above.
create a datasheet from 2 odbc linked tables which I will be exporting to Excel. The resulting datasheet will have four columns, 'Purchase Order Number' 'Stock Code' 'Delivery Date' 'Unit Price'. The information I require in the datasheet is a unique stock code (one occurrence of each stock code) with the most recent unit price based on the last delivery date for each product. The linked tables contain many Purchase Orders for the same stock codes over a time period of a number of years where the unit price has varied.
I have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard. But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007. I can't use the Package Wizard.
My application is protected with username and password. According to the user who has done the log in, some options will be available and some not.
Then, are there sessions in access?? How can I know who is loged in with which role otherwise?
My idea is to have a table, and say, loggin ok for the user X, but there may be one or more users at the same time. Then, how can I know which user is who if two are logged in in the same application by remote connection?
The first column is auto-incremented (primary key). We would like the last column to be a counter which identifies each session regarding a port number and a connexion number.
Is there a SQL or Access function which would allow us to do that?
I've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables Dim db As DAO.Database Dim qdf As DAO.QueryDef Dim varItem As Variant Dim strCriteria As String Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM qryContractListSummarybyDateContract3TYPEBREAK WHERE qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri Masonry NSW');'
After long, long, long hiatus of doing other stuff, I wanted to get around to update the database. One thing I had set up wrong was the attendance rosters.I just need to be able to create a new class, which may have more than one sessions, then make a list of registrants for a particular class, then be able to track their attendance per session for this class.However, my Google-Fu is lacking as every templates I've looked at doesn't really answer my question, which how three entities relate to each other.I know for sure that Class-Attendees is a one many relationship. Same attendee can register for more than one class, so that's no brainer. Likewise, Class-Session should be also be one many relationship for obvious reasons. However, if I relate Session to Attendee, it would create a circular relationship between the three entities. I've toyed with the idea of having a hierarchial tables of Class -> Attendees -> Sessions, but that does not relate the sessions to the class, which is necessary. I wonder if I should create a fourth table to contain attendances and use Session and Attendees as FK, but that still wouldn't fix the possiblity of a circular relationship?Any insights will be greatly appreciated. TIA
I'm trying to return a list of students in a particular team who have not attended a certain number of sessions at a gym, between two dates. For some reason i get the error. At most one record can be returned by this subquery. (Error 3354).
SELECT [Student ID], Count(*) AS ["Number of Times Attended"] FROM Gym_Attendance WHERE [Gym Date] BETWEEN [Forms]![SV_Attendance]![txtStart].Value AND [Forms]![SV_Attendance]![txtEnd].Value AND [Student ID] Like (SELECT [Student ID] FROM Student_Sports WHERE [Sporting Team] = [Forms]![SV_Attendance]![lstTeam].Value) GROUP BY [Student ID] HAVING Count(*) < [Forms]![SV_Attendance]![txtNo].Value;
I have a module in my database that creates an appointment based on a table of sessions. The module works in all respects, except two:
1) When I declare optional attendees it sometimes shows them as required attendees in the actual meeting in outlook, but not always
2) The .Send method does not seem to work. It creates the appointment on my calendar as the originator of the appointment, but does not send to the other recipients.
Below is the code:
Code: Private Sub SchedOutlook() Dim rsEmployee As DAO.Recordset Set rsEmployee = CurrentDb.OpenRecordset("Select * FROM Employee INNER JOIN tblSession ON Employee.EmpID = tblSession.EmpID;", dbOpenDynaset) Dim rsMentor As DAO.Recordset
I have spent the last couple of days trying to figure out how to make this work.
I have three tables.
tblIntakeMain [IntakeMainID]
tblIncidentDetails [IncidentdeatailsID]
tblPersonnel [PersonnelID]
On the main form I use subforms to link tblIncidentDetails and tblPersonnel to tblIntakeMain. Both subforms can, and do, have many entries. This all works fine. What is not working is the search form I am using.
I am using Gromits most excellent Search Form. The problem is when I create a query, qSearch, to bring together the three tables I get a multiple records which makes the searches very confusing and near useless. Is there anyway around this? Is there something I am missing? Is there another search method I could use that would work in a similar way as Gromits? Please help before the Prozac runs out and I lose my mind--what little it left.
Hi everyone. Apologies if this has come up before, but the search terms I've tried here and on google keep turning up the wrong information.
At work I manage a large database with many tables. It stores data for participants in a research study. Each table stores the data for a different test, so one participant may have multiple records. Primary keys for these tables are defined by a combination of the participant and date of test fields. (Everything is dependent upon a table that stores the static info for participants, so the database is normalized.)
I want to be able to make a table that lists target participants and dates, and then create a query that looks at this table and pulls all the available data from various tables for those individuals that was recorded within one year of the target dates.
I've successfully made queries that meet these criteria while pulling data from only one table. The problem I'm having is that when I try to pull from multiple tables, each with it's own date field that needs to be used as a criterion, I end up excluding almost all the data, because most of the target participants do not have all the requested data within the target dates.
I've tried being inclusive with my criteria (using ORs), but then I end up with tons of data that I don't want and I need to filter through it, which defeats the purpose of the query.
Any advice on handling this issue, or do I basically just need to create a separate query for each table?
I'm sorry if this is too vague, but it's illegal for me to upload any of my own dataset. I could probably come up with an example if it's helpful, though.
The company have MS Access 2003, Office XP Professional with Front Page, and Office XP Developer. But, we don't have license on Office XP Professional with front page, others have license. I installed MS Access 2003, and Office Xp Developer on my company machine, when I use Office XP Developer to create the package/access runtime for my clients, it must refer to Office XP Professional with front page to create Access Runtime. But, I don't have license for Office XP with front page, whereas I have license for Office XP Developer. So, after I finished creating the package, Is the Access Runtime legal in rules distribute to my clients using?
I have access 2003 installed, which I use to make systems ( doh )
Anyway, I have just installed Access Runtime on the same machine so that I can test my databases on the runtime version to make sure that all works ok. However, I have installed several times now, but I can not find runtime anywhere to run it... Can you not use runtime if you have full blown access installed ? Or am i just having a blonde moment ???
I have an application developed in Access 2000. Can anybody help with my search for the access runtime licence so that I can distribute to many users (who may not have access)? I have been told I need Visual Tool Extensions for Office but cant get an evaluation to check it works with my app.
OR, does anybody know a source (cheap obviously) of MS Access 2000 - users who dont have access only need 2000 to run this app.
Hi all. I have problem with form for viewing pictures. If I use apllication using full MS Access I haven't any problem. I can see BMP, JPG, GIF ... But if I open appllication using runtime I cannot open JPG file. Runtime show error to transfer picture to GIF or BMP. Where is the problem?
I have MS Access 2002 version, I create one mdb file and then put it on the sharing drive, I install Access RunTime on my client machines, they can run the mdb file on the sharing drive.
Another way, I used Office XP Developer Edtion to create package and then install the package on my client machines, they can run the mdb file.
Here is a question, Why do we need Office XP Developer Edition to create the package? Because we just install Access Runtime on the client machines, then they can run the mdb files.
Ive created a database using the file system object that creates folders, moves files from one folder to another, etc.
This works perfectly on my home pc, but when i try to install it on the server at work I get the following error message:-
Runtime Error 429
Active X component can't create object
I've had a look on the net and appears that it only happens on certain computers and I wondered if anyone had any quick fixes that they had come across over the years.
So I made a little db using A2k3 to use @ work. We have OpenOffice.org 2.0 @ work and not MS Office. Since I knew Access better than OO's db program, I used it and was going to just take it in and use it after it was finished. Well, I didn't realize that unlike OO's Word, PowerPoint and Excel versions, it's Access version does NOT open it's MS equivalent - Access db's. It'll link to them and use data, but all tables, forms, reports, etc have to be designed in the OO environment. Geez!! So I looked @ getting the Access Runtime. It's a bit expensive from what I read (about $200 if I read correctly). I have a couple questions. First, is it really that expensive? Second, is there another solution to this problem? Third, I read that the 2007 runtime may be free. Is that so? If so, will it work backwards - with a 2003 db? Thank you, thank you, thank you.
if I don't buy office Developer software, I just download Access Runtime 2002 from the Microsoft website, and then install it on the client machines. Do I commit the company rules? Do I need to buy unlimited license for Access Runtime before installing?
I have full version MS Access, and Office Developer Edition to disribute the Access RunTime for my clients.
I don't want to create the package (adp file), I just want to create the package for Access RunTime, and then install it into my client machines, we want to run the same adp file on the network sharing drive. Then, it's fine. But, how do I install the supported files into my client machines? Because the supported files attached to the package (adp file), if we install adp file into the client machine, it will install adp file and the supported files, but we don't want to install adp file, we just want to install supported files.