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....
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 have a database with a form. The form has quite a bit of code. This database is on a network. On some of the computers the Form will not open. When I go into Microsoft Visual Basic Tools References I am finding the following.
MISSING: Microsoft CDO 1.21 Library MISSING: Microsfot ActiveX Data Objects 2.1 Library
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?
I cannot get this code to run in access 2010. It shows no missing references, but errors that Object required.
Dim wshShell, btn Set wshShell = WSCript.CreateObject("WScript.Shell") btn = wshShell.PopUp("Filter data wil be removed.", 2, "Data Unfilter:", &H4 + &H20) Select Case btn
With the help of many people on this forum, my database is coming along well (Thank you!). My DB will end up on a server where it will be accessed. My question is; should I use the replica function, or back up the file every day or so.
The database I am replacing has been a replica and it always looses data. I am not sure it is because its a replica or not.
I am still new to Access and am loving the learning process. I am stuck on a problem though. I have serached the forums here and various other places and haven't found the info I am looking for. I was wondering if there is a way to have a relpica (or a seperate database that can syncronize) that has a modied design. I want the main one to have everything on it, reports/forms/ add/delete/ect, but I want another one that is simply a data entry form, with only the option to input data. I would love to do this and avoid system security measures with usernames and passwords. From my reading it doesn't seem like I can do this, but I still hold in my heart a glimmer of hope. Please help, and if you can explain the process to me, all the better (its how I'm learning).
Am using a replica set in order to distribute a school reporting system around teaching staff.
Everything works fine apart from one thing. A marking system (basically 1 to 6 list) is stored in a linked table. Before replication this appears in the correct order. Once the database has been replicated however the list is placed in a random order and I cannot rectify this.
With only 6 items this is not much of a problem but I also want to use a much longer list and the same problem appears.
Can anyone explain why this happens and if there is a simple way to get around it?
Am really only an Access novice and I really appreciate any help that you could give me.
I know how to setup a Replica's Priority, but where do I go if I want to change it afterwards? I have searched everywhere, or am I just supposed to create another replica and set it then?
I currently have a database thats A Replica which I need to Convert Back to a Normal Data file, Is there a simple way of doing this other than creating a new db with tables then using Querys to add the data from the replica.
I'm using 2002 and the replica if sized around 470Mb with over 200 Tables.
also does anybody know if the file size for assess 2002 was incresed from access 2000's 2Gb.
I am getting this error on a access 97 database that we have been using for years. the message just started popping. use are still able to access the database, yet this message will not got away.
this member of the replica set has expired because it hasn't been syncronized with another m ember of the replica set.
Using access 2003 my replica set tables in both the master and replicas seems to have lost the key field! The data and field itself are simply missing from every table. When I look at the data in the tables the key field called 'UID' is not visible but I can still see it in the relationships view and in certain forms and queries. If I try to re join any of the two tables the UID field comes up as an option to join the two with but it's still not visible in any of the tables.
I have been using replication successfully for years. Recently the PC where my Design Master resided crashed taking the hard drive with it. No problems I thought, I used a replica to recover the design master and placed it on the new hard drive (the OS and Access was upgraded from 2000 to XP, however the Access 2000 file format was retained – there are still a couple of laptops with only W2000 software). I understand that moving the path of replicas or design masters is no no, so I proceeded to start from scratch and create a complete new batch of replicas based from the new design master.
Everything was going to plan UNTIL a replica was routinely synchronized with the design master. The design master reverted back to a replica. I recovered the design master again, everything looking fine until again a synchronization causes the design master revert to replica.
Next plan of attack to hopefully fix a potential corruption problem: create a new blank database, import all (non-system) tables, compact and repair, and create a new replica from scratch. From the design master, I created the complementing replicas and sure enough the Design Master again reverted to a Replica after a routine synchronization.
I repeated this “start from scratch” procedure, and the same results prevailed. I am at a loss especially since I verified that the hidden system MSysReplicas table had only two entries after the Design Master and Replica were first created.
I would greatly appreciate any ideas of where to go next with this problem.
I have a replica at work, 1 copy on the network, 1 local.. I need to add a column to the main table, getting "Operation is not supported for this type of object".... I have users that use the database but was given a change to the form/report which requires a column addition. What is the simplest way to get around this??? I'm trying not to get into major problems.
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@&^^#%$@).
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.
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
This is an ongoing problem I have had for 4 weeks now.
I have made a a system thats acts like a clock In/clock out Out system.
the structure is somthing like this ID Username tblDailyLog TimeIn MorningBreakOut MorningBreakOut LunchOut LunchIn AfternoonOut AfternoonIn TimeOut
All fields apart from ID (autonumber) and username (String*255) are Date field (there are a few others like DateOfTimesheet etc but they arnt important here)
When a user arrives in the morning they make a record which they use for the day
They then have a form with a whole bunch of buttons which simply updates the correct field. For example they click the "Sign in for the Day" button and it updates the correct field with the current time.
Everything was going fine until people noticed that every now and again a sign in time dissapeared.
I have hacked myself to death trying to solve this problem but still the updates go Astray.
Now each time a time is updated the process goes somthing like this
1. the user opens their timesheet for the day (the RS is SNAPSHOT and no locks)
2. User Hits a sign in/out button 3. The record source is changed to "" and all buttons hidden (to ensure the record isnt locked and to make sure you dont do two things at once) 3. The table is updated with the new time (using some dynamic SQL) 4. The table is repeatadly checked using a DO loop to make sure the the correct time went in. 5. when the returned time value of the field matches the varaible used to update it, the form is returned to normal and the user carries on his/her merry way (if it never matches the screen should crash but this never happens). 6. A New record is added to another table called "tblbugfixinglog" which records which field was updated and when. This is so that I have two records in two different ways (figured if one went astray I could pull it back off the other) 7. Another new record is added to yet another table called tblSQLRecord, which simply logs all .RUNSQL statements that are executed.
I thought that the two extra tables (and the check that the record had been updated) would help me track down where the records are going missing, but this isnt the case.
Now it appears that some records arnt being added to tblBugFixingLog and to tblSQLRecord either and some of these tables are getting quite a few #ERROR's in them..
None of the tables are related to any other and i've no idea how #ERROR lines are appearing in a table that has 1 function... to recieve new records ... no editing, no viewing, no deleting.
Does anyone have any idea how these updates/inserts can go missing or create #ERRORs. I've built plenty of Databases in my time and have never come across this. __________________________________________________ ______________
This is the function I use to add a record to tblBugfixingLog and tblSQLRecord
Private Sub AddBugLog(ByVal TimesheetNumber As Long, ByVal FieldUpdating As String, ByVal NewFieldValue) Dim TempSQL As String TempSQL = "INSERT INTO tblBugFixingLog (TimeAndDateOfEntrySERVER,TimeAndDateOfEntryPC,Fie ldUpdated,NewEntry,UserID,TimesheetNumber,Computer AssetNo) VALUES (" & _ "#" & Format(ServerGetTime(Environ$("LOGONSERVER"))) & "#," & _ "#" & Now & "#," & _ "'" & FieldUpdating & "'," & _ "'" & NewFieldValue & "'," & _ "'" & GetNTUser & "'," & _ "'" & TimesheetNumber & "'," & _ "'" & fOSMachineName & "')" ' MsgBox TempSQL DoCmd.RunSQL "INSERT INTO tblSQLRecord (Username,DateAndTime,Screen,TheSQL) VALUES('" & LoginInfo.sUsername & "','" & CStr(Now) & "','Add Bug Log function','" & CleanData(TempSQL) & "')", False 'CleanData is a function that removes ' and " from the SQL string so i can easily add the SQL string into the table DoCmd.RunSQL TempSQL, False End Sub
Public Function CleanData(ByVal DataToClean As String) Dim TempData As String Dim i As Integer TempData = "" For i = 1 To Len(DataToClean) Select Case Mid(DataToClean, i, 1) Case "'" TempData = TempData & "`" Case """" TempData = TempData & "`" Case Else TempData = TempData & Mid(DataToClean, i, 1) End Select Next i CleanData = TempData End Function
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.
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
