General :: Transfer Tables Directly To Backend Database?
Mar 12, 2013
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 recently designed a new database according an old database in order to replace it. I found that I have trouble transferring the data from old to new database.
Only transferring data from one table to another
Database A: [table]![customer] to Database B: [table]![Client]
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.
Then a query from the payment that shows student I'd,arrears,amount due,paid. And balance
My question is
1.How do I transfer the students and their balance to a new semester and session 2.Do I have to new student and payment tables every semester bcos payment are made every semester 3. I want to keep each students payment for as long as they remain in the school 4. A session is made up three semesters how do I transfer students to a new session
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.
I currently have a CSV Table consisting of 30 fields linked to my access database, now and again I need to add additional fields. but each time I do this I'm having to relink the csv and rename all the field names etc..
Is it possible for me to add a new field directly in the CSV files and quickly refresh the linked table in access to pick up the new field? I've tried the Table Linked Manager. but it doesnt pick up the new field
Is there a way to directly access a TWAIN compatible scanner directly from a form button in Access 2007/2010 so that it will add one or more images to the specific table?
I have a number of Excel spreadsheets (data sources) hosted on Sharepoint that I need to link to one single Access database.
At first. I cannot link the spreadsheets directly to Access because Access cannot read the spreadsheets on SharePoint to make the links.
Secondly, I can export the spreadsheets from SharePoint to a local folder on my PC and keep them 'refreshed'. The problem with this is that I cannot link Access to the local refreshed spreadsheets because of the (auto) extention .iqy. Access does not know the extention .iqy and hence the two cannot be linked at all.
Thus: How do I link an Excel spreadsheet hosted on SharePoint to MS Access.
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.
Im stuck on a project that I have received help on before. I am trying to E-Mail a daily report created by a macro in Access 2000. It needs to go out as an excel spreadsheet, but in a format that can be opened in a Blackberry. The advise i was given was to use Transferdatabase. This is where i become unstuck. No matter what I type where i come unstuck. Is there anyone out there that can possibly advise me what to do in "idiot proof" steps? Im afraid my knowledge of Access is limited to 2 weeks self taught knowhow ?
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.
I work in a hospital where each ward has its own identical but UNLINKED staff database. I wanted to make a single database but the management was adamant that for confidentiality they should each be standalone. I lost this argument!
Data is stored in 7 tables: Identity, annual leave, sick leave, qualifications, etc.
Too late, someone has realised that staff may transfer from one ward to another, so the whole record needs to be transferred. What's the best way to do this?
So far the process I have come up with is: Choose the person you wish to export from the source database Run 7 queries to export the records from the various tables e.g. to Excel Create linked tables in the target database to pick up these records Run import queries.
I set up a macro to run the 7 export queries, using the "OutputTo" action and specifying .xls for the output format. But the files created don't appear to be readable by Access. In Explorer, they only have the Windows icon and are just "files".
Does anyone know a better way to tackle this problem?
I work in a hospital where each ward has its own identical but UNLINKED staff database. I wanted to make a single database but the management was adamant that for confidentiality they should each be standalone. I lost this argument!
Data is stored in 7 tables: Identity, annual leave, sick leave, qualifications, etc.
Too late, someone has realised that staff may transfer from one ward to another, so the whole record needs to be transferred. What's the best way to do this?
So far the process I have come up with is: Choose the person you wish to export from the source database Run 7 queries to export the records from the various tables e.g. to Excel Create linked tables in the target database to pick up these records Run import queries.
I set up a macro to run the 7 export queries, using the "OutputTo" action and specifying .xls for the output format. But the files created don't appear to be readable by Access. In Explorer, they only have the Windows icon and are just "files".
Does anyone know a better way to tackle this problem?
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 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'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?
We've got a database that was on an old computer (Windows 98), and we wanted to transfer this database to our new computers (Windows XP). The database transfers over fine, but there seems to be a problem.
When we try to run a report, it doesn't semem to work properly. We are a training agency and the report in question is designed to show the courses booked in for each tutor between two set dates. The dates are typed into a form (start date and end date), and the tutor can also be selected from this form, and then a report is generated.
Without dates being inputted, all the courses are shown (so the report is pages and pages long). This is working ok. However, when dates are inputted the report stops working and error messages appear on the report. Hence it seems to be a problem with the dates, but I can't understand what since all the boxes are exactly the same as the version on the other computer, and when transferred back to the other computer it also works fine.
Any help with what could be going wrong here would be GREATLY appreciated.
I have (on a company network) a FrontEnd .accde and a backend .accdb - currently ~ 10 users (some over wifi - slow!)The FrontEnd is becoming a rather large file ~ 10 MB and is also becoming slower.I am looking to separate this in to 3 FrontEnd files as to simplify and to lessen the file sizes etc.
My question is - are there any issues around a 3 x FrontEnd databases all connecting to 1 x backend database holding all the tables - over a network?
