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 have designed a split database( with back end and front end), I am just wondering what would be the best way to put a password for both of the back and front end.
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)
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...
I have a Back end (with password) which resides in a netdrive while the front end is installed in each individual users desktop, the problem is, some of the users netdrive was mapped in a different way (different letters..some are J others are G). I'm looking for code that I can relink the database to the front end in runtime, I did try to look in the net but I can't find anything that I can put the password as parameter.
this sample code from Dev is good, but i got an error because the database requires a password.where i can put the password?
Code:
Function fRefreshLinks(NewDbName As String) As Boolean Dim strMsg As String, collTbls As Collection Dim i As Integer, strDBPath As String, strTbl As String Dim dbCurr As Database, dbLink As Database Dim tdfLocal As TableDef
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?
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 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'm about to move to a back end / front end system, from a single database file. Before I do so, I want to make sure I have all bases covered so to speak.
My back end file will reside on a server. I am aware that path names are sometimes changed by network administrators without warning.
From tests, I notice that, if the path to the back end can't be found, one cannot open the front end database file at all (Access 2003).
My question is: if my back end file gets moved, or the path changed, how can I get into my front end file to update the linked tables.
I am trying to create a navigation form on a split database with front end and back end.But Access is not letting me drag forms or reports into the navigation form. Why?
Hi guys! I have a front-end (FE) linked to a back-end (BE) db. I have added a password to the BE, but the knock on effect is that the FE won't work now. Just says 'Invalid Password'. I'm using MS Access 2002.
Any help would be appreciatted.
(The password is to prevent unwanted users from deleting data on the BE 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.
Firstly thank you for your help, this should be a simple one I hope, but is cracking my head on the wall. Have searched and searched and can't find an answer.
I have an Access Db that is not password protected, but is asking for a password. It opens on any other machine fine?
I think my version of Access is playing funny buggers with me, any suggestions?
I was trying to implement some security on this Db, which is why it happened I'm sure. I ran the security wizard, set-up two users and admin with passwords, I have the output file to "recreate" something too.
Issue is, I then copied this Db to another computer for use on there, it worked without a Password, so didn't need to worry about it, now I can't open any Db on my machine??
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 need to take my database 50 miles to a factory site so that an engineer and I can review/modify all the records, ~450 so far.
Can I copy the front end and back end files to my laptop, review edit the data offsite, and then overwrite the back end file on my server when I get back? Are there any issues with doing that?
Does anyone know of a way to make a database back up by a click of a button in a main form in the database? (so a customer does not have to go tools/database utilities/back up database)
: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.
I am almost at the finishing line with a great deal of help from here. I have now normalised the tables, built complicated queries, forms, reports, all from scratch as I knew absolutely nothing before I started with Access three months ago. I have compacted and repaired the database using the wizard, and also complied the code and analyzed all tables, forms, queries, and reports and relationships. The final step is to make it an MDE file so that it can go on the local network at work (not on the internet). My questions are these;
Do I need to split the database into front and back ends?
If I save a copy of the original MDB file and then make it a MDE file would that not suffice in making it run more efficiently?
Can a split MDB database be made into an MDE database?
I have a database that resides on a file server share. I have split the database to create a backend. I then posted a shortcut of the front end to the desktops of two users who have access to the share. I then tried to access the front end from the two machines simultaneously. It opened on the first PC but not the second? When I viewed the server share it had a 'padlock' icon?
Where am I going wrong? This is the first time I have attempted this scenario!! Thanks in advance, Phil
Should splitting only be done when all tables,queries,forms,reports, etc. are done. Or can it be done anytime. I am almost to that stage but didnt want to jump the gun and run into problems later on.
I was having a discussion with Rickster57 concerning my newly developed database, and he recommended that I split it so that it has a front end and a back end. Rick listed a number of very good reasons for doing this (so I will definitely do it). But I wanted to pose the question so I could get some of the reasons the more seasoned Access programmers have for creating a front and back end to their programs.
I recently split my database and also used Bob Larson's Autoupdating tool. Everything appeared to be working fine until a few users were unable to access the db. I later found out that because they are at a different site, they don't map to the server that houses the database BE. However, even if they manually map to the correct server, they are unable to bring up the db Form. They get an error stating the BE "...is not a valid path". My questions are:
1) If I were to copy all the files (the Master FE, BE, and MDE) to a public folder that ALL users have access to, will everyone be able to bring up the database Form?
2) How would this affect what was already set up when I ran Bob Larson's utility (or even the splitting and MDE creation)?
3) Is there a way to "Undo" what was previously "Done" to this database (ie: Splitting, Larson Utility, MDE creation) in order to correct the issue, or do I need to start from scratch and split the database while it's on a Public drive.
I hope this makes sense. Thanks in advance for your help.
I just want to know that " How to split the Access database in Front End and Back End application"? I am creating a database that i want to store on server and simultaneously want to give access to 20 terminals (cleints) to access the database.
Secondly, I have to provide a field in a form "Document number". However as per the requirement user can enter "PIR No", "Serial No" or at times both as document number. Both the things "PIR No" and "Serial No" have different format types like "PIR No 001" and "Srl No001".
On basis of document number later i have to give the option to search the particular document. Please guide me how to provide the option to enter the field values.