I have used Microsoft’s Security FAQ and recommendations on this forum and build a split database; secured with one worgroup file for development and one for customers: what is the most appropriate way to upgrade the backend database content (tables mostly) (as the front-end database can just be replaced) at the customers site?
At the customer there is no development workgroup file, so no permissions to change database objects. I would really like to run sql updates from the new FE database. The solution I currently have devised to go around this problem, involves a lot of manual data moving code, to take care of referential integrity etc. However this approach has a higher risk of creating errors and also takes a lot longer time.
Is there something I have misunderstood of the Security FAQ or recommendation on this forum?
I am trying to compact & repair a secured database. I log in exclusively as the administrator with the following shortcut property target: "C:Program FilesMicrosoft OfficeOFFICE11MSACCESS.EXE" f:pathnameappname.mdb /User "adminname" /Pwd "adminpwd" /wrkgrp f:pathnameappname.mdw /excl
When I run Compact & Repair, I get the following message: "Microsoft Office Access can't delete f:pathnameappname.mdb after compacting it. The compacted database has been named f:pathnamedb1.mdb."
It goes on to say that it can't delete the original database because it is read-only (even though it is not).
Can I compact a secured database manually, or does it require some sort of utility?
I have an access database that was set with security about 10 years ago.
I have now created another database in 2010 and I am importing all the objects to make a clean non secured database.
When I import tables it imports system table objects like MSysRelationships, but as it already exists it adds another MSysRelationships with a 1 on the end (MSysRelationships1).
Should I delete the original MSysRelationships and then rename the MSysRelationships1 as MSysRelationships.
There are numerous others like MSysAccessstorage, MSysACEs etc...
I am gathering that if I don't rename MSysRelationships1to MSysRelationships then the relationship data would be incorrect and the database wouldn't work correctly, but maybe I am wrong.
I have been given the responsibility for a database that resides on a company network. The Database has been created by using Access 2000 in Windows XP. There are windows folders fro each team that needs use of the database and within these folders is a macro that loads the form for each team. There is a shortcut folder to the Admin Entrance point wher the actual database and tables_be are located. I have looked at both the properties of both these files and both are Access 2000 databases?
The Database called Database( not my choice of name ) contains all the forms, queries, reports,modules etc and the tables are linked to what seems to be the Admin Entrance point. Unfortunately I am unable to see the full link when using linked table manager. This I presume is the tables located in tables_be. The database table_be contains all the tables.
When trying to store the Autonumbering to the database after corruption using a solution kindly supplied by Pat Hartmann by taking a copy of both the database and table_be and working on these I successfully got the autonumbering working.
What do I need to do to successfully implemting these on the network. I have tried to copy the new files back to the network with the same names and in the same location but am getting error messages when I try access some of the forms.
Unfortuately there is no documentation as to how this database has been constructed hence the long winded post.
Hi - I have a front end database that is linked to 2 backend databases. I'd like to add code so that after the splashscreen pops up it checks to see if the front end is linked. If not then asks the user to enter the path for the two backend databases. I need your HELP!!1
A client has had a database in operation for about a year. They requested some updates. I have been trying to figure out an easy way to update table structer with out having the client go into the backend and add a field or two.
I wrote an update program, that copies the table from their backend, and copied it to the updated table and tried to copy it back to thier backend, but since it is in a relationship, it won't let me.
Hey guys... I created a reaaaally simple wages calculation program some time ago in VB6. When you click the save button, the records are saved to a .txt file stored in the same directoy as the program itself.
However, I'd like to take this a step further and connect this program with some tables setup in an Access database. I know this has something to do with ADO, right? But not quite sure how to set this up..
Would it be possible to get some guidance on this? If you'd like to see the program, let me know.
I've created a database to track my client information. I've split it into front end and back end databases. Everything there works fine so far.
I have other co-workers who track their own clients who I will be giving this database to. So we will soon have the same database with completely different data stored in them.
If I want to make changes in the future, I should easily be able to change the front end, get them a copy to install, and all should be well.
But what if I want to make changes to the backend? Like if I decide I want to track some completely new data in a separate table on the backend. I won't have the ability to just go out to the central server and change 1 backend database. There may be 10 identically structured backends on 10 different machines that all need the new table added to them, without effecting their unique data in the existing tables.
So, assuming my explaination made sense, is there a way to make backend changes like I'll need to? Or would I have to go to each backend database and manually make the changes?
Hallo everybody I have an Access databse in which I have devided the tables into backend and frontend by using the Database Splitter wizard. Then if I create any tables in the frontend Access file then thease tables are visible only in the front end of this system , not from other systems if I put the back end in network. its ok for some tables , but now I have a table which I have to put in the shared backend , but if I cerate in the front end it is visible only in front end and if I create in backend it is visible only in backend. how to send a table in the front end to backend after database splitting is over, so that I can access this table from other systems. if it is possible please help me. Thank you. Kiran
I have a database stored out on a shared drive at my company that multiple users connect to via a front end application that they save on their own hard drives. Recently I have noticed that the back end database keeps getting opened exclusively which prevents other users from being able to access the back-end database. For the life of me I cannot figure out what about the front end opens the back end exclusively and cannot find any plausible solutions I thought I could develop something that could force close a back-end database or disconnect all users from it?
I have a back end database that i cannot access at the moment. Is it possible to set the link of the tables for the front end application based on the location that the database will be even though i can't see that location now?
I'd like to to import some large oracle tables from a remote server using "DoCmd.TransferDatabase..." on a daily basis. Currently, the system works, but my database is getting quite large (800 Mb) and I'd like to split off the tables to a back end database.
Is there a way to import directly to the back end database? The postings that I've seen seem to imply that one must first import the tables into my front end, then export them into the back end. Does that sound correct?
I'm at home right now, but will give it a try when I get to work. It just seems like there's got to be a more direct way!
Jon Mulder Department of Water Resources Red Bluff, CA
I have a Ms Access split database where in the backend database grows up very fast and needs to be compressed everyday. I have written a batch script to compact the same and have scheduled it to be run every night. But the script is unable to compress the backend every time since the users tend to leave the application open at the end of the day. Ideally i am looking for a command line script to forcefully close the back end database if open before attempting to compact it.
I searched on web but could not find a command line script for forcefully closing the back end database.
I have an Access DB with a form that allows the user to select a new backend database. I can connect to the backend and then .refreshlinks but nothing on the form is updated. I have tried requiring the form but that doesn't do anything. I've tried loads of other things, refresh, recalc etc., but nothing updates the open form.
The only way I have managed to get it to work is to close the form and reopen it, then it shows the data from the newly linked backend database.
While it works, it doesn't look good but also there seems to be some problem with it because eventually it reports an error saying "cannot open any more databases" and when clicking OK comes back with "An error occurred while sending data to the OLE server (the application used to create the object" and a whole bunch of other messages.
I think it might have something to do with the fact that the form has a number of MS graphs open on it, but I'm not sure. Also, I can't track down a particular line of VBA code which causes this error.
how to update a form after changing the backend database.
I have a client that is using a split database. I am working on an update to the program and need to transfer a table to the backend that has the correct structure and information included in it. My thoughts are to make a one time use program that transfers the table to the backend. I have seen DoCmd.TransferDatabase and DoCmd.CopyObject as possible ways to go.
If I want to distribute a front end to connect with a MySQL back end ... do I need to set up the system DSN on each workstation that will be using the front end?
i have created a database with access 2003 that now experience some slowness problem. i have concluded that is a table that is becomed to big, but i can't delete any record...
it should help me upgrade the database to MSDE? if yes someone could help me?
So a while back I created a database which I use to keep track of my companies large list of products. It is very simple only 3 tables, 1 query and 1 form. After running into a problem with copying and pasting updates on each computer in the office I decided to split the database on a network drive. This worked for a bit, however I had to add new fields and modify the form, which corrupted the file. Luckily I had a backup before the split.
As far as I could tell all I had to do was modify the backend file and make a new front end. However it seems like it is not as easy as I thought it would be. How do you modify a split database without corrupting the files or using a non-split copy?
If I have an MS Access frontend that connects to an MS Access backend, is there a way to hide/permission block the pathway to the backend's folder but still allow access via the frontend db?
Right now I can't dedicate a server to a more "secure" form of DB or anything like that so I'm stuck with MS Access for now. I just don't want someone looking at, say, a link table path and then navigating to that folder and getting access to backend information.
Is there any particular reason I would choose to use
DoCmd.RunSQL "insert into...
Versus
CurrentDb.Execute "insert into.... ??
I am using an unbound form on the front end of my database to populate the backend tables (multiple tables). Some forms only have a few fields, while other forms have about 15 fields with 3-4 tables updating.
I am okay using the DoCmn.RunSQL , but I keeping reading on the forum that others chose CurrentDB.Execute and it has me thinking.
My database is stored on a network drive with only on front end.
