I 'm having trouble with a DB. One of the forms is a schuduler which the user clicks on a calendar control and a form opens up showing orders schuduled for that date and unschudule order. The user then can assign the order. Just recently whichout any DB changes the user gets kicked out of the db when they scroll down thru the records. This is happening on Multiple workstations and rebooting doesn't help. Tried deleting the record but its not a problem with a specific record scrolling thru other records with the same fields filled in works. The Detect and Repair did not work (believe it or not) The same happens on the query that the form get it data from and I tried to copy the table to make a backup but it kicks me out. I'm thinking the tbl might have to many fields (55) but the DB is only 39 MB.
I wasn't sure if this is the right spot for the probelm I'm having, but....
In Access 2000, I have an application with a Report selection menu, from where you can choose one or several reports, key in a from-date / to-date range, select whether to preview or print and then click a command button that'll run the selected reports.
Each report iws based on a its own group of queries.
Until today, everything was running OK, but today, when a certain report is selected, an hourglass stays on the screen for an awfully long time, and then I'm tossed out of my application and tossed out of Access completely! There are no errors displayed, there is nothing displayed.
If anyone has a hint of an idea, I'd sure love to hear what's causing this strange behavior. Thank you to anyone or any group of people who might be able to shed light on this!!! I think I need medication!!
I'm curious to know if it is possible to kick users off your db so you can make changes. Is it possible to send them a message to save and close within 30 seconds, or just send them a messgae. I guess I want to know whether I can 1) Kick a user off 2) Send them a message 3) Send a user a message and then kick them off
Ok this is weird but is there a way to kick everyone out of the database so you can do updates? Alot of times people tend to leave their computer on overnight with the database still open
Has anyone got any ideas of programs that are avaliable to kick users of a database in Access remotely?
Our Programmes team have a program which will do this and it doesn't involve any tables, etc within the database but they won't tell me whats it called or provide me with a copy of it!!
I've got a lady in San Francisco who has a MicroSoft Access database. She wrote some basic code to pull data from a SQL Server database into her Access database and then generate a bunch of reports.... She uses ODBC to communicate to the SQL Server database. All was working fine until this week and suddenly now when she runs the reporting job she gets a pop-up for each individual report asking her to log in fresh each time...
Has anyone experienced a similar problem or might have any idea how to fix this? Thanks in advance!
I have a form that we've been using for a while now. I want to add a multi-select box to find records on the form.
While this works great on other forms in our database, when I use the wizard on this particular form it doens't give me the "find a record on my form based on my selection option" but gives me...
"Look up values in a table or query" and "I will type in the values that I want"
instead. Why is the wizard not giving me the other option?
Also, my auto correct feature isn't working to stop all caps on data entry on one of my forms? How do I troubleshoot that?
I am using Access 2000 I have set some fields in a table to required However it still allows the cell to be blank But if I type a space into the cell, then the rule kicks in
Hello, I would like to use the FindRecord Method, but something does not work. I would like to find a record which contains the data I entered in an unbound textbox in the form. The action should be started by a command button. As 'Find what'-object I used '=[text61].[text]. Thanks for your help.
Hello, I would like to insert a DCount function in an unbound textbox in a form to count all records in a query. My current code in the textbox is: '=DCount("*","Query1")'. The Query 'Query1' depends on two parameters, which has to be entered before opening the query. The result is '#Error', if 'Query1' is open or not. Thanks for your help.
does anyone know how to get a serial cash drawer with kick back interface to open through Access? any help or a point in the right direction will be hugely appreciated
I created a database which had to be split to allow multiple people to access it with three 'front-ends' so that different people had different levels of access. Due to security problems this database had to be moved to another location on the network. Now I have used the linked table manager to update all of the frontends so they can locate the data. Previously users would just copy their own version, appropriate to them, and use this to update; now though only one person can open the database at a time with the backend database being opened and hence locked (if that makes sense).
Any suggestions as to why this has happened, or solutions would be appreciated.
I maintain the Access databases at the hospital that I work at. Last weekend, our server went down. Computer Services got a new server and reworked the networking permissions. However, Access will no longer allow more than one user to open the database at a time. This is a problem because we always have multiple users that need simultaneous access. The default is still "Open Shared" and I checked to ensure that the databases are not being opened exclusively. However, the message that I do get when a second user tries to open the database is:
The table 'MSysAccessObjects' is already opened exclusively by another user, or it is already open through the user interface and cannot be manipulated programmatically. (Error 3008) -
I understand that this message usually comes up when I try to open a table that is already being edited elsewhere. I have the record locks set to "edited record". However, this is a system file, so I am hesitant to make changes in it unless I know exactly what I am doing. This is a problem that we have never had before but for some reason was created after our server went down. I don't know why something changed or if this table is absolutely necessary. I am unsure where to start to solve the problem.
