Can anyone shed light on why my Database seems to have stopped working so far as I've a combo box on a main form, which provides one half of a PK/FK relationship. The subform displays one or more records for this value. However, I've just entered the same 'value' (string) for an entry in the combo box as another, which shouldn't display any records in the subform yet - but it displays the records of the first combo 'entry'. This important thing is that the key's are all unique (I've doubled checked this), so why does it seem to not work?
Please.
I've split a database and the backend relationships are still intact but the front end they are not and it looks like this is causing a problem. Is this usual?
I'm (as said before) totally new to everything that has to do with programming, and therefore I work in the visual way, and thus I need to have the reports shown in relations in order to work with it...
After designing the database that mean after creating all the tables and when pressed on relations buttuon it shows a diagram with relations established. Is this a kind of ERD. in this it shows relations between entities so can we call that an ERD?
Hi there, I'm a bit stuck on this but it should be pretty easy.
Say I have a table secondHandCar - this contains infromation on the makeID (eg 123), price, number of doors. Now each car can have a number of images, this number isn't set so I have an images table...
tbl_secondHandCar makeID - key price number of doors
Now clearly I have a problem: the images table is going to have many makeIDs with different images. I've just got stuck here - do I need an image id or something? But then my make ID will still repeat in tbl_images.
Hi, I'm trying to build a mdb which holds customer details, which insurance they have, who sold them this and which Insurance company provided this. The relations I have to make are driving me nuts ! When I try to enter a new customer in a Form, there is a advisor added, the package the customer wants is added. But this shouldn't happen for the advisor and the package allready exists !
Who can help me with the proper relations ? Attached is screendump of the current relations.
I have a DB and for some reason queries aren't working properly. My guess is the table relationships I made. If anyone else has an idea on changing my relationships so that all forms and queries will work to thier full potential please give my DB a look.
I would create a one-on-one relationship between coGeneralContactID and coPostContactsID. And now I can create my one-on-many relationships between from the Postalcodes table.
1) Is this clever? 2) Should both these fields have a key? 3) I set coGeneralContactID to autonumbering and coPostContactsID to numeric. is this also correct. 4) I also use prefixes before the fieldnames 'cp-' for 'ContactsPost' is this naming convention ok? I think it makes programming easier. But are there condingstandards for that in Access/VBA?
I have 3 tables Metrics, FixedExpenses, Variable Expenses, I want them all to have a date in a form, and a subform for all the records to be added. I want to be able to do this without having 3 seperate date tables linked to the other three tables. I am not sure how to do this correctly. (I want to be able to see all the records for a certain day in these forms.)
I have a table named [Brand] and several tables named [Brand@@@Models], one for each field in the Brand table.I want each field from the [Brand] table to be related to it's specific Model table. I thought like that so I don't have a Brand#1 related to Brand#2 models, etc.. I didn't want to have all the models for all the brands in a single table, was I right to think like this?
I was editing one of my forms, which is something i do often normally without a hitch, and once i'd finished i noticed that my find contact and add new contact and also delete contact buttons had stopped working. These are all totally basic buttons made with the control box wizards by the way. During editing i cut and pasted one of the labels away from the data box so that i could position it without the actual data box moving along with it. then once i had it where i wanted it i re-associated it with the data field/box. This is what i suspect caused the problem.
Anyway, i've tried removing the broken buttons and creating new ones but i still get the same error.
here is the error in all its glory.
http://www.ntj9.co.uk/access_error.jpg
i've tried some stuff i found on ms knowledgebase but didn't have any luck so i hope you can help me people.
When I added some Access 2003 (Winows XP) machines to our Access 2000 (on Windows 2k)-based database, many of them would not operate some of the Switchboard "buttons" (especially for reports that contained macros). The animation of "click" would operate, but nothing would happen, no form or report would occur like it should.
After several rounds with Microsoft's Access Help guys, here's how we "fixed" it: 1. I deleted all printers from the affected user's computer. 2. I booted into SAFE MODE with NETWORKING, then installed the Windows-based GENERIC TEXT printer. 3. I rebooted into XP and installed the GENERIC TEXT printer there also, for the affected users. 4. I re-installed the usual office printers around our office.
This completely fixed the problem on all XP-based computers. The technician at Microsoft says he cannot explain WHY this works, but I have experienced that it DOES work, so try it if you're having troubles, too. It's some kind of mysterious workaround that "fixes" Windows XP somehow.
HI: I have a db with about 70 tables in it. I am trying to see the relationships among say, 40 of them, all at once. I like the view of the relationship window but: I cant scale it, select multiple tables and reposition them, use the mouse wheel to move it (only the window sliders), and, I have to click on a table entry to allow me to reposition the table (should'nt I just have to click on the table outline itself?). This is a really awakward thing to use. Also, I can't seem to 'Shrink to fit' the relationship window when I print it. Is it cockpit error or just really broken? Any way to make it easier to work with? (or, did I choose the wrong DB tool for the job?)
I have a database which has been running well for four years. There are four tables that are linked from one to another in a one-to-many relationship, i.e., Table1 to Table2 to Table3 to Table4. We recently had a power failure and our network went down. Now the relationship between Table2 and Table3 is broken. When I try to rejoin them using the Relationship View, Access tells me that the relationship between the tables is "Indeterminate". I have run queries testing for unmatched records between all of the tables and the data appears to be fine.
My only guess at this point is that the structure of one of the tables is corrupted. The problem is that each of the tables has an autonumber field. If I build a new table structure, and append my old data, isn't that going to renumber all of the records?
I have run a compact and repair on the database and that didn't help. I have made copies of the tables and tried to use them in the relationships. The copies don't work either. Other than not being able to link the two tables, everything is working fine.
I am having trouble with a simple data base where I have 1 main form with 1 sub form, but when I try to use the form (go from design view to datasheet view) I get the message
Error Accessing File Network Connection May have been lost.
and the link between the form and the code seems to have been lost ... I can no longer edit the vb code (it keeps reverting back no matter what I type).
When I delete the form, the VB entry remains - (since it is no longer linked with the form). Running the database this way I get error messages saying there is a Macro with a misspelled name (ie: it can't find the form with the name).
The only way I have been able to get rid of it is to create a new form with nothing in it, save it and then delete it.
Really frustrating!!!!
Any ideas on how I can get rid of this problem, best ways to re-build the data base (I have created a new one, imported the tables and created new forms from scratch ... then this problem comes back@&^^#%$@).
The following code is being used to pull in the Name from the previous record into the current record. It works GREAT for 28 records, and then it starts just pulling random names from the source table. Can you tell me what I'm doing wrong? Thank you!Private Sub Form_Current()
Dim s As String Dim db As New ADODB.Connection Dim rs As New ADODB.Recordset Set db = CurrentProject.Connection
s = "SELECT Last(ERName) AS ERName FROM [Staffing]"
Set rs = New ADODB.Recordset rs.Open s, db, adOpenDynamic, adLockOptimistic 'add to the table
With rs Me![ERName] = .Fields("ERName") End With Set rs = Nothing Set db = Nothing
missing or broken reference to the file ‘plugin.ocx’ version 1.0, and also in file 'msoutl.olb version 9.2’
It says I need to fix these references to ensure the database or project works properly.
(The references shown as MISSING in the Visual Basic Editor are:
Microsoft Active X Plugin
Microsoft Outlook 11.0 Object Library)
Clicking OK lets me into the database and all seems to work fine. However, the last thing I want is for the whole thing to fall over and become corrupt so any assistance would be greatly appreciated.
I've search the forum but couldn't find anything on this, maybe someone can point me in the right direction...
My application consist of two Access files: Front End & Back End. The front end is linked to the back end using Linked Table Manager. A problem arise last week when the IT renamed one of the folder in the program path, as a result, the Front End file cannot find the Back End file (I guess the links were static). So I had to relink the tables manually and got it working again. However, in the future, I won't be around to relink the tables, and my client doesn't know how to do this (and I don't want them to have to do this every time the folder is moved).
My question is, is there a way to link it so that it will adapt to path name changes. The two files are in the same folder.
I am looking for something like: when the front end opens, if the link is broken, it relinks it to the data file in its current database folder. Thanks.
Love this forum! It orginally helped me build a database to manage customers back in 2002 (using Access 2002). Becuase of our slow server, I was forced to spilt the database and it's been great for years (some glitches). Recently one of the users upgraded to Access 2003. When he sync's to the master file, the master has problems. "...contains a missing or broken reference to the file 'OWC10.DLL' version 1.1" I reviewed the references and it's looking for Microsoft Outlook 11, instead of 10. When other users sync, everyone now inherits this problem. Do you have any ideas for a solution so I don't have to fix reference problems? All users will eventually be on Access 2003 so having him stop using it would only be a temporary solution. Is there a patch or upgrade to fix this problem? Any help? thanks in advance....
Hi everyone, Im building a database as part of a group project for uni. Its almost finished but recently on first opening the DB and clicking on a button on the form we get the following message boxes:
Firstly:
Your database contains a missing or broken reference to the file ‘OWC10.DLL’ version 1.1.
Click ok
and get...
Your database contains a missing or broken reference to the file ‘MSCHRT20.OCX’ version 2.0
When i click help it talks about deleting references but im not sure how to do this as im no expert by any means! :rolleyes: I think this problem may have arisen because our accountancy department computers use access 2003 and the rest of the uni uses xp and we have been working on them both - oops! :(
Anyways i was wondering if anyone could point me in the right direction to fix these problems?
Hi I've noticed totally different behavior with my secured databases in 98 and in XP.
In XP Access Security works. In 98 it is broken.
For example today I secured a database. I went to another computer running 98 and Access 2002 that was joined to the default workgroup file system.mdw . They still had full access to the database and were not even asked to enter a login. Once I joined the correct workgroup file the security was implemented though. (In XP if I go back to the Default workgroup file the security is still maintained.)
So strange. Where is the security if it is totally ignored on 98 operatings systems? Someone can just make a copy of the database and have full access in 98 despite the database being secured.
Peter.
Hi I've noticed totally different behavior with my secured databases in 98 and in XP.
In XP Access Security works. In 98 it is broken.
For example today I secured a database. I went to another computer running 98 and Access 2002 that was joined to the default workgroup file system.mdw . They still had full access to the database and were not even asked to enter a login. Once I joined the correct workgroup file the security was implemented though. (In XP if I go back to the Default workgroup file the security is still maintained.)
So strange. Where is the security if it is totally ignored on 98 operatings systems? Someone can just make a copy of the database and have full access in 98 despite the database being secured.
Peter.
Then your db is not really [correctly] secured. You should get the same result by copying the database to another computer and the user should be able to open the db without using your workgroup file. Sounds like you have joined your computer to your custom workgroup file [or worse, you have modified the default "System.mdw" file on your computer with your new security settings. Search around the forum for you problem has been asked and answered in many other threads.
ghudson is correct. The behavior you describe occurs whenever you connect to a DB using the default SYSTEM.MDW file. I have answered this question beaucoup times, so look up posts on "Security" where I have contributed comments.
To understand why this occurs, you need to know one more thing: The name of your workgroup is a registry function. You would see the same behavior when you move the .MDB to an XP machine but never join the correct workgroup on that machine. (Because, of course, the registry entry isn't changed until you JOIN the workgroup.)
Your database is not properly secured. Take a look at the Security FAQ document. Search the kb or you may find a link from here.
Why are you double posting?
At least Pat gave you the same answers as your first posting recieved... http://www.access-programmers.co.uk/forums/showthread.php?t=107458
I have been asked to take a database created last year and re-design it to make it more user-friendly. Not a problem, I thought when asked but I am running into a little problem...(the database designer) In my opinion, to make a system more user-friendly there is a necessity to access the code and tables in order to gain a reasonable knowledge of the way in which it has been constructed. Unfortunately, although I am allowed to LOOK at the front end, I am not allowed any further access to coding or back end information. At present middle management are siding with the database designer as they feel that from a security standpoint, access needs controlling (I can agree with this to an extent) Does anyone have any ideas of how I can talk the management round or any suggestions for a way through this issue? (Oh, and I'm not allowed to build them a new database and substitute it...I already asked)
I have been asked to look into fixing a permissions problem with a database. The company has been in the process of updating the OS on our computers.
The database in question is stored on a shared network drive. It opens fine on a windows XP machine running Access 2003 but when the same user tries to open the database from windows 7 using access 2010, the message: "You do not have the necessary permissions to use the '<file path>' object. Have your system administrator or the person who created this object establish the appropriate permissions for you."
