I have a database that runs a macro/report every 2 hours, however our network has been up and down lately. This causes the macro to fail when trying to log into the system because the table that is storing your username is no longer in the database. When I check, all tables, linked tables, forms, reports, macros and modules are all gone. I find the only way to get them back is to close the database and reopen.
What I want is a way to reconnect the objects without closing and reopening.
It seems to be quite simple really. Make a form for Orders and add a subform for Order items. Write some VB code to chage values on the Order form when an Order item is added or amended. Add a "Find" dropdown to the Order form to find particular Order numbers.
Run the form and add/amend orders and items. This will work OK. Move to the next or subsequent order using the "Next" button. Add/Amend again - no problem. Drop down the "Find" control, select an order and the correct order comes up on the form. Amend an item. As the code attempts to change a text box on the Order form Access crashes.
The same code (to add up the items, take off discount and add on tax) can be run after a "Find" by changing a "Discount %" text box on the Order form and this works OK. Perhaps the Order form needs to be in focus for the code to work but I cannot see why this should be so.
In fact you don't actually need the "Find" dropdown. Any code that moves to another Order record programatically will cause Access to crash when an item is added/edited subsequently.
Making it crash is simple but stopping it has cost me a couple of days of frustation. Has anybody any ideas?
My Access 2000 project crashed and the computer dutifully asked to report the error to Microsoft, so I let it run. I then looked at the subsequent screen and was surprised. Well - silly me, maybe I shouldn't have been.:mad:
This screen simply said that Access 2000 was in "extended support" and my "solution" was to upgrade to a newer version. This was a bit irritating since the purpose of reporting feedback is to provide an opportunity to fix program bugs. So why ask the user to provide an error report if that report will simply be ignored and only used for a sales pitch.
While Microsoft has every right to discontinue product development, I would hope that they would still try to fix bugs that cause a program to crash. I guess Microsoft's quality control department has been outsourced to the same company that Dilbert works for. Additionally, I find euphemisms, such as "extended support" for "You are out of any help options, tough luck" to be quite irritating. Why not directly admit that we are on our own.
Also I am still on a slow boil over over the last six years by the fact that help for DAO/ADO disappeared from Access 2000 help which was in Acess97 help and Microsoft never got around to making it available as an update.
So, my database appeared to be working OK yesterday however I occasionally saw an error in my "Update Event" script on one of my combo boxes. today, now when I try the combo box, I get a immediate crash.If im assuming its the same combo box, here is the code for that box:
Code:
Private Sub MCAcmb_AfterUpdate() Me.Model.RowSource = "SELECT DISTINCT [tbl].Record, [tbl].Model" & _ " FROM [tbl] WHERE Record = '" & Me.Recordcmb.Value & _ "' ORDER BY Model"
[code]...
I recently added a header...just tried it again and got the error:"The expression After Update you entered as the event property setting produced the following error:Object or class does not support the set of events."however I got it to work by entering VB, adding a space, removing it and then saving and entering the form view the form worked as normal. when i close and reload, i get the error again
Background Info: I developed our main department's Access 2003 split database which is on a server for 15+ Users. I've now been given Access 2007 for development -- Users still have 2003. There are also 2 other smaller databases that are not split (.mdb).
Problem: In the split database, I've saved the Application .mdb as 2003, relinked and made a new .mde. But the Users still cannot open the database. (I did this in a copy until I figure out the nuances with 2007.) The 2 other unsplit databases can be saved as 2003 version and Users can open OK.
I'm grateful for any suggestions on working with Access 2007. I've been trying to tackle the ribbon which is a whole other question.
I have an Access 2000/2003 database which opens up and displays correctly in Access 2007, but when I go to use the File>Print command, or for that matter any of the other pull down menu's nothing happens?
Has anyone else experienced thisproblem, or does anyone know what I am doing wrong?
Greeting All, I am trying the beta version of Access 2007 and realize that when converting Access 97 to Access 2007, the new db in Access 2007 has an extension of .accdb. I rename the db file name to xxxxx.mdb and the VB app fails to recognize it.
Is there any way to convert the xxxx.accdb (Access 2007 beta) to xxxx.mdb so that I can try my app against the Access 2007 db?????
I am kinda new to 2007 and have at the moment a simple database.
I want three things
A: Use the database on a server.
B: Restrict the use to users etc as i used to be a ble to do in Access 97 i think (do i have to make a MDW if so how ?) 9I tried ACCDE but does not seem to do anything)
C: When users use the datavase not see all the normal access editing stuf..
I have a DB which has been up and running with no problems for a couple of months.
A couple of users have recently had new machines installed. These are XP SP2 with Office 2000.
The Database FE is on the PC and the Backend is on the server.
When FE is first downloaded and opened it runs fine. The second time you go in the DB gets by the Splash screen but then crashes on the Title Menu. If you then recopy the FE to the machine it opens fine the first time then crashes again on the second attempt.
I have checked the references and all ok. I have full error trapping on the Splash screen and the Title Menu yet I just get the error "Access has encountered an error and needs to close..."
It runs fine on my machine which is XP SP2 with Office 2002. Has anyone any suggestions that I can check or repair this?
Just upgraded to Acccess 2007 and have ownership problem extracting queries from a 2002 db.
When trying to import into a new 2007 or export from the 2002, get "you have no permission" message
Have created a new user tried to change owner of the db, but no permission File security looks correct in that I am owner of the file with full permissions, but Access doesn't recognize me as the owner
Tried logging in as admin, but it isn't the owner either
This is not critical, just very time consuming, this is a test project, but it would be nice not to have to rewrite about 30-40 queries and equivalent forms
I am not sure where to post this question. I remember finding a forum just for Microsoft Access 2007 questions, but I couldn't find it again... Indifferent
Anyway, I have created a database, and have been testing it with my application. I have some data in this database. I was wondering if there was a way in Microsoft Access 2007 to create an empty copy of the database for release. In other words, I would like to create a copy of the database with all of the tables and columns, but without the data (rows) that I had entered as part of using my testing database...
Does anyone know if I can do this?
If anyone knows where this Access 2007 forum is, or resources that might answer my question, please let me know, as I would greatly appreciate that.
I'm using Access 2007 which I built a database that runs queries off of tables using ODBC. The database is all done in ms access, I've used no visual basic programing on it. I'm now trying to move a copy of the database to another computer's local drive in the office. When we try to open it on the other computer it gives me an error that says "There was a problem sending the command to the program" and Access hangs, which I then have to run task manager to end the program.
Specs Are: Windows 7 64bit (the db was created on Windows 7 32bit)
I have created a database in Access 2010 and I am not able to open the same database in Access 2007. I have read somewhere that it is possible to open. I get the message, " Unrecognized database format". In Access options, the default file format is, "Access 2007".
focking pissed off. i want to add an image to a some forms, the database is all working and that. but when i put a picture in in the design view and then go to view it the whole thing crashs. i nearly lost the whole data base from putting one on the home page, thank fock i had a back up and now ionly have to redo one form as the other one wont open anymore it will just crash every time i try to open it. i have no idea whats going on, i have other images that i put on it before, but i cant put any on now. anyone every encounted this and how do i over come it!
I'm using Access 2007, with what I think is a normal database that I've built up over the past month (maybe 15 tables, <1000 records, 20 queries, 4 or 5 reports and macros). I'm not an experienced Access programmer, so I don't think I'm doing anything fancy with security settings or any other such stuff. (If I have, it's surely by accident, not by intent.)
When I try to back up the db using the simple office button -> manage -> backup method, access generates a date-stamped backup filename and opens a file save dialog for me, but it ALWAYS fails to backup the database. I always get the same error message when I click save, whether I save on my machine, or on a network drive.
"Could not use '<path to the current database dir><backname>.accdb; file already in use."
This same error occurs when I create a new blank database with a single Table1 in it, so I don't think it's my database.
Does anyone have any idea why this might be happening? I scoured the net for help, but nothing. I checked various Access forums, but nothing. So I arrive here after I've done my homework... thanks
I want to hide the top toolbars when my users open my database in Access 2007! i have an autoexec macro to maximise the window which gets rid of the navigation bar on the side but cant work out how to hide the top bar? do i need to write code? if so what code and where would i input it.. any help would be much appreciated...
I am on a deadline today and when I went to open an Access 2007 (I abhor the fact that I am forced to use 2007) database, it will not open. It gives me the error message Unrecognized database format [file path].
I have tried creating a brand new database and importing all objects from old to new but I get the same error message.
employee personal recordemployee job statusleave recordinventory record issue to employeejob performanceinventory control of equipmentforms, queries, tables, login forms.
I work with an Access 2007 database that I split into a front end and back end. The back end holds all of the tables and the front end holds the queries, forms and reports. It is also a multi-user database, in that we have 14 people having access to the same back end. Each of the 14 people have their own front end. I have one main table in the back end listing clients and their individual ID numbers. That table has a One to Many relationship with several other tables, such as Case Notes and Authorizations, to name a couple.
Here's one of my problems: Sometimes data that is entered by a user will disappear.
Example 1: User creates a new record in the Authorizations form. Sometimes it is created by duplicating an existing record, sometimes it is completely new. User then prints a report from that new record, which looks like it has been saved. A couple minutes later, or a couple hours later, or maybe even the next day, user goes back into the database and cannot find the record that was previously created. At that time I look in the back end and cannot find the record either.
Example 2: User creates a new record in the Case Notes form on Day 1. These are always completely new records. User returns to the database on Day 2 and the new record sometimes does not show up in the form or in the back end table.
I cannot MAKE these things happen and they are sporadic, which makes it hard to diagnose, but why this was happening or if there was a way to retrieve the lost data.
I've been experiencing a very frustrating problem recently.
One of my databases crahes randomly, and I'd like to know if some of you have tips to helps me.
The database is splited in front-end and back-end, both on the server. I know keeping the front-end on the client PC will improve performance, but due to a high number of users (about 60 to 80) and the need of doing frequent updates, installing the front-end on each machines is not an option for now.
Users are not all directly connected to the server. Those who are directly connecte4d to the server (in building A) have no problem. Those who don't (building B) have extensive lags on opening (about 30 seconds), and on about anything that calls an heavy query, most often leeding to a crash. Access display the message telling that the datbase needs to be repaired and restart.
I tryed several thing to improve my queries, like eleminating most of GROUP BY and UNIQUE clauses and avoiding the use of functions.
I have a lot of conditional formatting in the forms, but I don't think this is the problem, since it is executed on the local machine (as far as I know).
My theory is that the lags cause some call to the DB to timeout. I just dont know how to fix that. Is there an option to higher the timeout delay?
My other theory is that the problem is caused by dropped packets during the connection to the DB. I tryed downloading large files (100Mb to 250Mb) from the server several times and never had a problem. Although the connection is quite slow, the ping is very small, like below 10ms to 20ms. Is there better ways to test a network connection, if possible without installing software (limited rights on the machine)?
Would using Replicas be a solution? What are the pros and cons of it? I never used them and know very little about it. My idea would be of putting a back-end on both servers, but I guess the data would not be as live.
BTW, I am using Access 2002 (2000 file format) on an XP SP2 PC.
Thanks to all of you patient enough to read all of this! I Hope some of you have some awnsers, tips or tricks!
I've got a bit of a problem with linking a text box to a ComboBox. I have an employee name in a field [EmployeeName] that sits in the Header of a Form. (This is so I can show multiple records for that employee without having their name repeated at each one). I also have the name of contact [ContactName] that sits in the Detail area of the form.Both names come from their own tables that have all their contact numbers and e-mail addresses in columns I have linked the name to text boxes [ContactPhone] & [EmployeePhone] with their relevant phone numbers in within the Detail area of the form.
The ContactPhone that has the ContactName within the Details part of the form works well with no problems by putting =[ContactName].Column(1) in the Control Source
However when I put =[EmployeeName].Column(1) in the relevant Control Source (and / or EmployeeEMail in a second text box), once I have saved the form in Design view and returned to Form view, Access crashes and shuts down!If I remove the wording from the control source Access doesn't crash.
"how to COMPACT the DB by introducing delay of 10 seconds and then close the DB".In the Database, I'm able to accomplish the "Compact" the database using the function below.
Function Compact() SendKeys "%(FMC)", False End Function
As my DB is quite huge, the Compact action takes around 10 seconds to complete.Now, i would like to Close the Database after Compacting the DB. I tried including "DoCmd.Quit" in the function. The commands in the function, closes the DB but the Compact function doesn't seem to have executed as it needs 10 seconds to complete.
Function Compact() SendKeys "%(FMC)", False DoCmd.Quit End Function
how to introduce this delay of 10 seconds and then close the DB.
I have a standard shared Access DB application (i.e. central BE on the network, multiple users running their own copy of the FE on their local machine) Has been in production for a while, no major issues.
New user has been added in recent weeks. My error logger has picked up an error he hit earlier today - doesn't appear to have been fatal (he hasn't come to me with a problem, suggesting he just "OK"d the error prompt and continued on - I need to confirm this with him though...)
Error was 3343 "Unrecognized database format 'C:TempMyDBMyDB.accde'."
Can see it was tripped on a particular form which queries certain data into a subform (so he was obviously able to open the FE and connect to the BE fine; it was several steps down the road where the error has occurred).
