Hi, I am not sure where to put this thread hopefully someone here can help me.
I have spent a good deal of time developing a very effective access database for a client. It is split into a front end and back end and connected using the Linked Table Manager when necessary.
The front end is quite loaded with queries, reports, forms, macros etc and the back end simply has the tables.
The front end is about 15 mb and the back about 8 mb.
Current set up is a small workgroup network with about 4 -5 consecutive users at any one given time.
I am looking for some advice on how to set up or facilitate getting the backend on the internet so anyone with a front end can access it outside of the LAN.
Today I set up an account with WebDrive which can connect to and assign a drive letter on your pc to any FTP, HTTP site.
I made the connection with WebDrive and using the linked table manager successfully linked the tables on my local machine to the back end on the FTP server - and actually ran the database at a pretty good rate.
I noticed however that it was downloading the backend to my local pc and once I closed the (a) form it was uploading the data back to the server? Very slow and often threw errors.
This of course is not what I wanted. Has anyone heard of doing this? Any work arounds or setting params would be greatly appreciated.
I have been told to create the DB in ASP but I do not have any idea on how to do that whatsoever...
So the database I have right now is split, with the back end on our server. Everything has been going great, however there are several second time delays when loading large forms, queries, etc. I've heard that moving the back end to an sql server is the way to go for speed.All forms and queries are on front end of database. Tables are located on the back end which is sitting on the server.
I'm looking into buying SQL Server 2014 Standard Edition.I would like to move my split end back end to the SQL Server, however I'm having a little confusion with all the different licensing out there.I have 20 computers that will be accessing the SQL Server.
I am new to split database format... If I put the backend on say windows server 2000 or 2003 in a folder, is there anything else I need to do? Any setting on the server?? Or do I need a specific type of server os ie sql server etc?
I have done the mistake of not keeping a backup, what I did is split my database file access and then created my mde file, I need to change some data on my tables, but I get the msg that I cant edit a linked table, is there a way that I could put things back the way it was, also this path that was created is it possible to change for future purposes (I might have to move the dir into a different path)
I have a database already split and I wanted to put a password on the back end. When I open up the front end and try to navigate through the forms it says "Not a valid password".Is there somewhere I need to go / something I need to do to link up the two now that a password has been created?
I am trying to use VBA to backup the BACK-END of a split database (so I can automatically archive selected data). If I use FileCopy I get a message that the BACK-END database has not been found.Obviously I could 'unlink' the BACK-END, copy it and 're-link' it..Is it possible to copy the BACK-END tables(not just the links) into the FRONT-END and get at them that way?
I am currently working on an application where I am using MS access as my FE and working with linked tables to SQL server BE. I also have a few temp tables within Access that are not linked but needed.
1. What are my steps into making this into a SPLIT DB? I am assume the BE will have my linked tables from SQL and the FE will have my temp tables and forms. Is this correct? 2. Once I split it, then I can make an .ACCDE file for a Mulit User environment, is this correct?
I have a split database. I have secured the mde sufficiently but I need to secure the back end so that no one could link to tables in it. If I introduce a password to the back end is this going to require those using front end to supply the password? If not then this could be good solution.
As the database is on the network drive, is there any other way to prevent people to link to the db? Can I hide the db in the network drive? Or should I hide tables in the BE. Should these still be available to be linked?
I hope this isn't too stupid a question, but I have a db that needs to be accessed from several workstations. It is currently a split db, with the backend residing on one of the workstations in the workgroup. I was wondering if it possible (as I am looking at buying a server) to "house" the backend on a Linux machine? The main reason I ask is that Linux is <$100, but MS Server is >$1000. Does the server need to be able to run the program? If yes, is there any way around this?
Hi I have 5 PC clients and a server.each user upon shutting down his PC,is prompted to send all the information inside a table "Patron" to a table inside the server.That way each user backs up his information to a table inside the server and at the end of the day,the table on the server side contains all the data from the 5 PCs.I am new to access,can anyone guide me through the steps I need to accomplish this project? thanks in advance
We have offices in other states that need to be able to open our data base. Due to the line speed it is extremely slow linking to our backend. Is it possible to have duplicate backends that can be merged, lets say over night or at the push of a button.
I'm experimenting with MS Access, and I've successfully split an MDB someone created into two files. I can access the database from 2 computers at once using the front end file connecting to a file server which hosts the _be.mdb file.
Could the _be.mdb file theoretically be on a NAS without any computer attached, or is there some runtime or full version of Access that needs to run on the machine with the back end file?
Cannot open back end database. There are no other users logged on Tried opening it in open exclusive mode but still error message. Front end on number of desktop PC's. Back End on server. I need to get in design mode on back end but won't let me. I get logon screen but when try to log on get message below I can log onto front end ok.
Error message something like.
* You do not have perimission to open or enable database * You must have open/run open/exclussive administer permissions. * Request other users to log off e.t.c.
I have created a few split multiuser databases in Access 97 that my company has used over the past few years. Currently, we are trying to move everything to a new network server. When I did a simple copy and paste on Friday moving everything to the other server it seemed to work fine. Until I tried to open any of the databases. I kept getting the message that they all were read only.
Do I need to bring the database back together before transferring it? I also plan on converting the databases to Access 2003. What precautions should I take in doing this?
Thanks for any and all information you can pass along.
At work a few of us all need to access the database to edit/update etc and at the moment only one of us can use it at once.We are getting a server in the near future so we will all be able to access it at the same time but I was wondering if there is an alternative way to do this in the meantime? I have been looking at "shared folders" but am unsure if they are suitable or how they work.
:confused: I have read a quite a few threads on spiting the database. My database is 50 Meg and running very slow. I have compacted and repair, still the same. This just happen all of sudden. Could that be possible?. What should I look out before I try to spit it?. Itís given that I will make a backup. I am running Access 2003. I have over 150 users.