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.
Anyone have any ideas?
Matt
hi!
i got a table containing info of 2 different products. and now i would like to split it so that each table only for 1 product.
but there is query based on the original table, the question is after splitting, and updating the query, the form doesn't work properly any longer...
a bigger problem is the form created based on that query has loads of vb code doing quotation, so it is costly to remake it...
thanks in advance
I'm on a project to build a database for the stores in our area. Things like managers, banks, and partners obviously should be in seperate tables. Most of the information though, seems to belong directly in a table of stores. Basically each record is a store and there will be very many attributes per record (about 30+). Some attributes only relate to certain departments and only someone from that department should see that info. If I broke up the big table into smaller tables it would be the same information but every table would have to have the store number to link it all back together. From a design standpoint this is bad because the store number is redundant.
So my question is, is it a good idea to split up the table for security purposes?
My main concern is security, I can take a hit on performance or storage.
I have one table with the following fieldsName, Address1, Address2, Postcodewhen data has been imported from Excel I have found error in the data entryie the excel spreadsheet contain Name, but the address has been entered into the Address1 field now I need to split into Address1 and Address 2. Please Help:confused:. I am beginner to access have never used VBA only some queries. So sorry but I will need to know exactly how to do it. Thanks so very much for your help. Sometimes a comma seperates the address but sometimes just a space
View 4 Replies View RelatedI am working on a project that requires to calculate interest on the amount. There are 2 tables, 1 with Interest rate for a product for different and periods and another is product table with amounts in different period.
Table 1 (Rates table)
Product From To Rate
1111 1/1/2012 1/20/2012 .75
1111 1/20/2012 1/28/2012 .50
1111 1/28/2012 4/6/2012 .40
Table 2 (Product table)
Product From To Amount
1111 1/1/2012 1/17/2012 10000
1111 1/17/2012 1/24/2012 15000
1111 1/24/2012 2/25/2012 20000
What i need to do is to calculate interset based on the above 2 table and insert into another table (Interest). However, the problem is with identifying correct rates for the periods in Table 2.
Eg.
for period 1/1 to 1/17: applicable rate would be .75
for period 1/17 to 1/24: From 1/17 to 1/20 the rate would be .75 and from 1/20 to 1/24 it would be .50
this is what i want to achieve, basically to split the period between 1/17 to 1/24 into 2 so that appropriate rate can be applied.
Hi,
To avoid the mind-numbing tedium of have to use make-table queries loads of times, is there a quick (probably VBA-related) way to split a large Access table, of about 350000 records, down into 93 smaller tables, based on a key code field that identifies each group of records e.g. GBW102, GBE999, etc?
Any help much appreciated.
thanks,
Alex
I have a database composed of personal statistics. (name, age, height, wt, etc). I have two attachment fields. Photos and Videos. Each of these fields can contain more that one file. The size of the video attachments is starting to get me up close to the 2 GB database limit. If each attachment field contained only one file, I would convert the fields over to a path link. I'm stumped on how to move the files out of the main database to control the size, but maintain the multi-file link to my forms. How to restructure this?
View 4 Replies View Relatedokay, last question. I promise. You all have been so helpful, though...
I have been given the assignment of splitting down a table into two more tables(three in total). My question is this: Could I use the Table analyzer? If so, what are the shortcomings? I would like to have the other tables referenced by the key of the original table instead of a lookup field, whioch I'm not sure if I can do in the analyzer. What attracts me to the analyzer is that it would make the needed queries to join the new tables. If I don't use the analyzer, would I use a make table query to accomplish it? If so, would I have to change every existing query in the database that used that old table?
I know it's a lot, but any help in pointing me in the right direction would be much appreciated
I want to split a table into multiple sets based on rowcount. Suppose I have a table having 10,000 records. I want different sets which should have values based on rowcount. Suppose if I select set 1 then the table should populate records from 1-2500. If I select set 2 then the table should automatically give the records from 2501-5000. If i select set3 then the table should have values from 5001-7500 and so on.
View 3 Replies View RelatedI'm trying to split a table up because I now realize it won't be able to do what I need in the future. It wasn't designed properly at the outset, and I'm trying to correct it now.
This is a database of pregnancies and deliveries.
The single table does not cater well for multiple pregnancies (twins, triplets, etc), and also I foresee problems when mothers come back in future for another delivery.
Therefore I am trying to separate data into 3 tables: Mother, Delivery and Baby.
This is because each mother can deliver more than once, and each delivery can have more than one baby.
I have set up a trial database, with just a few fields in each table to see if this works. An screenshot of the table relationships is attached.
The primary key of the Mother table is linked to the Delivery table, and ditto the primary key of the Delivery table and the Baby table.
I'm not sure how to migrate the data over, in terms of the primary keys of each table, because in the new tables, these should be an AutoNumber field, so that they are unique numbers.
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.
Hello,
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.
Your help is much appreciated
I am trying to split my database but when i run the database splitter it comes up with the following error messages:
Subscript out of range
And
Invalid procedure call or arguement
Does anyone have any ideas what could be causing these or how to fix it?
Thanks
Hi
How can I change the location of the back end part, at the moment the front end is looking for the back end at a different location
Cheers
Bikeboardsurf
Hi,
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.
Any help would be much appreciated.
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?
Thanks very much,
Hi,
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?
Any help will be very much appreciated.
B
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
Thanks
I have 2 questions.
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?
Can someone enlighten me on these few things?
Thanks
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.
Thanks.
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
View 3 Replies View Related