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.
I created a database with 10 tables and 8 relationships. Then, I learned about the Autonumber field type and decided that I wanted that to be the primary key of one of my existing tables, for a field that was already linked to 2 other tables. I had to delete the relationships and the original field to make the change, and Access said it had to delete an index, too. Now, Access won't allow me to re-establish those relationships.
I found that I had to change the fields in the other tables to match the Autonumber type and name of the original field, but now I am getting an error message stating, "Invalid field definition 'CustomerID' in definition of index or relationship. What does that mean? The field types and names are all the same.
I have a database with a number of linked tables that are linked to tables in different databases (not a back-end).for example, I have table1 that is linked to table1 in K:databasedb1.mdb.table2 linked to table2 in S:datadata.mdb.and so on...
However, recently we have moved all our databases to a new location.
K:databasedb1.mdb is now residing in O:masterdatabase and S:datadata.mdb is now residing in O:masterdata and so on...
I'm now in charge of relinking all those tables to point to the new location.I would do this in linked table manager one by one but we have 100s of tables linked to multiple different databases in different location.is there a way to create a VBA code that will automatically do this re-linking process?
so, 1. find unlinkable tables 2. search its new location under O:master 3. re-link it to the new location
Database names and tables names have not been changed. Just the location of databases.
I have developed a Microsoft Access 2010 database for my client and the database is split with Front-end/Back-end, the Back-end and the database is shared on Network, The client operating system and applications for all users are hosted and consistent and the service is delivered over Citrix.
The database some times corrupt the tables record and give a permanent #Delete Error, I have attached one of the database table and the screenshot of the error,
I have split database (B/E is in the SharePoint library, F/E has users on a local PCs). Sometimes, when I update/add data (does not matter if it is via form or directly in the table) it looks OK, but when I re-open the database, the data are gone.
Problem is that I cannot catch the moment when data were not saved (sometimes data are saved, sometimes not). I can point out this: if I re-enter the missing data, primary key continues subsequently, it looks like the data have never been entered. I tried to use script
Code: If Me.Dirty Then Me.Dirty = False
on "On Close" form event, does not work.
B/E is linked by VBA code and it looks OK (no error, Link Manager shows correct path). I suspect interrupted connetion to the SharePoint but I don't know how to check it. I implemented VBA script co keep open connection to the SP but the issue persists.
I have linked tables from SQL Server using ODBC connection that their location never changes. I have used certain fields of those tables to create queries and make table queries to derive to the information I needed.
On these tables on SQL Server, there is new data added daily. Every day, midnight, there's new data records added of whatever transactions took place in that working day. how often do I need to refresh linked tables in this case to get the latest data added. I mean, once I am linked, the make table query using those defined fields, would it get the latest data added by default when the query is executed, or I must refresh linked tables using Linked Table Manager and then run make table query.
Also, if I want the access to automatically refresh linked tables, can I use the following code? I have added this code, and executing it through a button, but I don't see anything happen, the database becomes inactive for couple seconds (I guess while it is updating) but I don't know is it updating the tables for sure or not, though I am not receiving any error when executing the code through the button.
Function RefreshLinkedTables() Dim tdf As TableDef For Each tdf In CurrentDb.TableDefs If Len(tdf.Connect) > 0 Then tdf.RefreshLink End If Next td End Function
I have linked tables in my db at the moment that rely on user dsn connections to an SQL server. I've been reading about DSNLess connections and want to try convert what i have to have permanent DSNless connections, but the code I've found doesn't appear to be working.
I've removed server specific details where i felt necessary, but when running the code i have it in place.
Code:
Public Sub RefreshODBCLinks() Dim connString As String Dim db As DAO.Database Dim tb As DAO.TableDef connString = "DRIVER=SQL Server;SERVER=<database ip address>;DATABASE=<
I have a split database.(Access 2010).Three of the linked tables are Appointments, Appointments_OLD, Appointments_NEW.
I want to use vba to rename Appointments as Appointments_OLD (replacing the current one) and to rename Appointments_NEW as Appointments (replacing the current one)
I have used:
'replace Appointments_OLD by Appointments, replace Appointments by Appointments_NEW DoCmd.Rename "Appointments_OLD", acTable, "Appointments" DoCmd.CopyObject , "Appointments", acTable, , "Appointments_NEW"
Unfortunately this just made Appointments and Appointments_NEW clones of one another - changes in one automatically occur in the other.
What I actually want to do is to swap the names round in the backend database while maintaining the right links to the frontend.
Hello All, I currently have a bunch of tables that I have linked to a SQL database. For development purposes (easy of use), I'd like to turn all those tables into regular tables rather than linked so if I take the db offsite, all the data is with me. I realize there will be no updates, etc. but that really doesn't matter for my needs in this case.
Is there a script or an easy way to do this? (besides doing a manual import for a LOT of tables)
I've tried searching but I might not be searching for the correct terminology.
looking for a way to export the list of table names, table types & if they are linked (e.g. tbl Sales Linked .dbf or tbl Staff linked to excel) from a database - this has to be done for about 300 databases.
in an individual db, I have a make table query off of the table MSysObjects to get the data. The Database field tells me where the source of the linked table resides & the ForeignName field gives me an idea of the format of the data source (e.g. dbf or excel). I could manually import that query into each db, run it to get the table names, then copy & paste..
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
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 one database called asset management. It consists of one main table called cyber assets. Most fields in this table are linked to a manually created lookup table inorder to restrict user input. There are also two additional, none lookup, tables used to list a) the IP addresses (there can be more than one) and b) another similar 1 to many type table. Basically this DB is used to manage basic cyber asset data, excluding most items related to configuration management.
So, this above DB serves the purposes of asset management. Now I essentially need a similar DB for Patch Management. What I've done for this is to assess each patch initially (i.e. just by looking at the patch title and determining if we even have any of those device. i.e. this assessment is not based on OS, model number... just a general 'may' or 'may not' be applicable). Here's what this SEPARATE DB looked like:
Since each patch is essentially assessed against itself, or maybe a better way to describe it is against the users memory of what we do and don't have, only a single table and form was needed.
So now we've been thru this process and the DB is filled, all initial assessments are complete. The next step is to take all the ones that are applicable to our company (based on the initial assessment when you answer, yes is applicable) and do assessments based on each device we have.So what I want to do is to link the two DBs on a new table called Patches_by_device, inside the original patching DB... so the relationships would look like this:
But as you can see, the linked table CYBER_ASSETS has some sort of undefined relationship type, which is causing my issues.So the next thing I did was to autocreate a form based on the Patches_by_device table, and here's the result.I need to change the patch_key to the Patch_ID+Patch description+URL, etc, and to change the device key to the the UNID+IP+functional description, etc...so I changed the form record source like this:
Now I should be able to change the control source of the Patch_key and Device_key to more useful information. so I changed: Patch_key control source to Patch_ID and Device_key control source to UNID (which is in the cyber assets table)
As you can see, it worked for the patch_ID but not the UNID which is part of the linked table.Must it be within one DB, because we have a ton of other modules to implement (e.g. config management, vulnerability assessments, audit stuff, and more...) and I'd like all these to be in individual DBs, all liked back to the main cyber_assets/Asset management DB.I've considered just modifying that patch table so that each device has its own column heading in the table, but this will cause issues when new devices are added.
I am taking over a database someone else created but is no longer here. The tables are linked to an external oracle database. I know the links exist because when I run a query it prompts me for my user name and password. However, the tables look like regular tables. There is no icon showing it's a linked table so I don't know which tables are actually linked and pulling from the Oracle database.
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)
