About 4500 records in a database have two names in a forename field, I need to split these so only the first name stays there and anything else in that field is moved to 'othername'.
Using Access, and update queries, I just can't work out what to do. Using Query Analyser I can see a logic but can't get the syntax right.
What I need is omething like
Code:SELECT * from individuals WHERE forename is like * *Dim pa, pbpa = the bit before the " "pb is the bit following the first " " and including any subsequent onesforename = paothernames = pb
Some forenames have simple problems (eg 'John Peter') others are less simple (eg 'Mr J P and Mrs S P')
I want to split the name field in Access database to 3 different columns Lname, Firstname and Middle name/initial.
Below is some sample records with Lname,First name and Middle Initial/name. PETERS M.D., WILLIAM A. III BOUCEK, ROBERT J. JR. MANSURD, ABDULRAZZAK BADDIGAM, KRISHNAMOHAN R. ABD EL AZIZ,AHMAD MOHAMAD MEMON,MOHAMMED SALEEM BREN-FIELDING,ALEXANDRIA ABD EL AZIZ, AHMAD MOHAMAD VAN GENUGTEN, RENATE E. CHESNUT, CHARLES HAILE IV LAW, MICHAEL W. Y. NGUYEN, DAO VAN NGHIEM STA. MARIA GANAL, JULIUS R CAWAGAS, LAURITO JR LABIO Please let me know.
I have a form with several data fields on it. I also have a button on the form that allows the user to duplicate a record . The reason for this duplication is so that if there will be an additional client record for the same customer, but only one piece of data will need to be changed, it's easier to copy the record and then change the one field.
However, I am getting the following message:
"some of the field names you tried to paste don't match fieldnames on the form"
and then not all data in all fields gets duplicated.
I need to figure this out, but am going nuts with it. If anyone has an idea or two they'd care to toss my way, I would be happy.
Getting ready to split a DB. No security really needed... Only the ability for multiple users needed. From what I have read here so far it seems best to use a MDE file on the front end and MDB file on the back end. One question is still not answered... I guess I will find out when I load the front ends on different stations.. BUT... I would like to know what to expect. I am assuming that each computer that I load the front end on I will have to go through and link the backend. Correct? I read a MS Knowledge base article about a form to do this... Is this only possible if you use the "developers edition" ??? Whats the common method for this task? Thanks Curtis
I have created an application that uses all the 'normal' factors of an access app. My forms are triggered by events that initiate some vba code which executes and then does something. No big whoop, we are all doing this; but I am going freakin' insane keeping up with changes. The users are using this app in a "live" test enviroment and the changes/updates are coming in quicker than I can type. "This field is not right it should read like this" Well I can't change it until everyone gets out - they don't like this answer:D
I jumped in before thinking a few versions ahead and did not split the database :eek: I have read a lot of posts here and other sites and I can tell that I need to split this app but am a bit hesitant. From what I can gather I would have a Front-End - houses all my queries and forms Back-End - houses all my tables
I have a few modules, where would they need to go so that I can work on them independent of what my users are doing? I would give each user a copy of the FE or make it available via network drive; would I then keep a seperate copy of my FE to make changes? If yes, does this mean my modules would be in the FE? Can I split the db now that it has been in live production? What are some common errors that I should look for prior to? I tried to split the db one time before, but my drop down list box(s) on the forms would not work. They are controlled by a query, not any code. Error msg stated could not find xyz sorry I don't recall the exact error
I need the ability to change, work on and update at will AND NOT effect my users.
I have been reading a lot about splitting databases on this forum. I still have some questions. 1) Will the FE (Front End) still show the tables? 2) Will users still be able to edit the forms, reports, etc.? 3) Will my code be hidden 4) Will all the users have up to date data showing when they open the Database? 5) Can more than one person open and input data in the database at the same time?
I also want to make an MDE copy, do I split first or make the MDE and then split?
The whole point is the following: I want the people (maximum 10) that will be using this database to only be able to do enter and view data. They should be able to generate the reports but not create new reports. I only want ONE person to be able to edit the forms, code, and reports. How would I do this.
I've split a database and the backend relationships are still intact but the front end they are not and it looks like this is causing a problem. Is this usual?
I've currently got a date of birth field in my database, but would like to query on just the birth month. Can anyone tell me how to do it. Do I have to create another field which separates out the month, and if so, how do I do that.
Hi everybody, I have been spending the last few days trying to find a way through the "access security Maze" which I believe I have just done. I have been following the "Ms Access Security Faq to the letter" and just now, I can open the database via a desktop shortcut including a custom workgroup address and I think everything is working fine. Now, I am trying to organise the next step which is splitting the application.
GHudson stated: I find it easier to start out with one database that has everything in it [including the security]. Then I copy the db. Rename them so that one is the front end, one is the back end. The security will still be in both since they are exact copies. Then remove the shared tables from the front end, remove everything else from the back end [except the tables that will be shared]. Then relink the shared tables from the front end to the back end.
Using custom shortcuts will make it easier for the users to open the front end with the correct workgroup. You can customize the shortcuts target field with all the required file and workgroup info.
I Understand prtty well what's being said but am getting a bit confused of where and how the different part of the application should be organised on the network:
*The back end file should be on the network drive(drive F) -That's fine...
*The front end should be distributed only on the station using the application:
1) Does that mean that I could place the FE on the F drive for a short while and ask the different user to copy the application and past it on their own drive and then delete the FE of the share drive.
2) I will have to use the custom shortcut with the specific work group on each station. Should they all have the same shortcut which would mean that there is only one FE on the F drive and not make much sense or Should the shortcut link to the FE application save on their drive which doesn't make much sense either because they could open the DataBase without the shortcut with their own "default" Workgroup and wouldn't be secure anymore.
I apologize for my confusion and have probably missed a basic step in my reasonning but if anybody could redirect me in the right direction, I would really be gratefull.
I setup my security (or lack there of, hehe) and split the database. I relinked the tables.
Now, Access gets hung up when I try to create an MDE of the FE to distribute. It starts the process, asking me to select a folder and file name, I do that, and it gets no further in the process. Access says (not responding).
Should I have created the MDE before I split it? Or does crashing of Access have nothing to do with whether i create the MDE before or after splitting?
Hi, hope someone here has experience with this issue.
Our system was recently converted to much tighter secured network environment and moved to Office 2003 (still Windows XP).
Within the next couple of weeks we expect to split/secure our new db for shared use across a network (approx. 6-8 users at any one time).
I want to keep the db in 2000 as long as possible because I'm doing lots of the work at home and that's what I have. After deployment there will be lots more changes but in managed releases. (sounds official, eh?...)
Does anyone know of any risks I'm running by keeping it in 2000 within Access2003?
I have been searching for more info on this and found out quite a lot about it; however, I am still wondering how to connect the front ends that will be in different machines to the back end that resides on server.
I know that when you split a database, the wizard asks where to save the first front end. But how about if you have many?
Can anyone help me to split a number using an access query to the left and right of the decimal point. I found it in a reference somewhere but have lost it. the number is generated in a query and I need to do something with the fraction
The first is regarding splitting a database into 2 files, one for tables, and one for forms and queries. I have a database whose data will be accessed from about 4 computers, and almost never will this data be accessed concurrently. In that kind of situation, is it easier to just put the whole DB in a share and give each user a shortcut to it, or should I be splitting it and just putting the tables on the share?
Second question:
The option in Access 2007 to make the database an .accde file. From what I understand this just locks down the structure of the database so it can't be changed. Is this correct? Can it be edited by an admin once it's converted to this format, or does it just stay that way? I guess if it can't be edited, one could just keep a copy of the .mdb, modify that, then reconvert it to .accde.
Also, if I were to split my DB, would I first split and then convert to ACCDE, or the opposite?
i thank all for helping with the issue of mulitple users. after i did the splitthe database using the wizard. i noticed the tables lookes diiferent. but how do i put the front ends for users in their document since am on a thin client enviromemt. or how do i transfer the front from the end. do i have to write codes?? thanks
Hi. I would like to split my database which is used by various people on a shared drive.
Is it possible to specify a relative path to the linked tables in the back end?
Otherwise, if people access the shared drive via different drive letters, it fails.
Also, I like to keep a copy of the database myself. With absolute paths to the back end tables, I can't simply copy both sections from one place to another - as the links fail.
i have a linked table from which i run an append query to produce a list of customer addresses. However the address appears in one field i.e addressline1 addressline2 etc and when displayed on a report it looks poor! is there any way that i can split this data out into 3 or 4 fields so they are displayed better on a report? Thanks
I recently decided to split my database into a front end/back end environment. What I noticed though was a huge slow down in performance. One subform in particular takes 5-8 seconds to load, as opposed to less than a second before the split.
I know that splitting the database comes highly recommended in this forum, but the slowness is unacceptable. I especially want to split the database so I can execute changes quicker.
By the way, I have read several threads that recommend turning off the name autocorrect feature. I did this in the front and back end but did not notice a diference. I also compact/repair the database regularly.
The other thing I tried was creating an MDE file, as I was told they run quicker. Unfortunately, I am told by Access that it cannot be created. I believe from what I have read that I have too many forms that have attached modules.
For now, I am going to merge the database back into one file. But if anyone could offer some advise, I would like to pursue a split again.
Hi, i have a table that has contact information in.
It has contact name, number etc and company.
Quite alot have the same company. I was hoping to split the table into two, a company and contact table which are linked. I've been thinking about this and not too sure how to go about it.
I am normalizing data from a spreadsheet of just over 4000 records. The spreadsheet has a "Model" field that contains both the model number and a model description, separated by a space. I would like to split this field into two different fields: "Model_Number" and "Model_Description". The model number is one word of varying lenths.
I have a dataset with an age field which just stored an age. I want to run a query which will calculate the frequency based on all age groups 20-30,30-40.
I have a column in a table that contains the date and the time, i want to be able to split this column into 2 so i have one column for date and one for time
