I have a group of part number doesn't come with a standard format. It is very tricky since some does come with some regular flow but some are not. Therefore i try to take 2 different sample category.
My idea is to split the LPN into 3 column eg. CIVUS (Type), 0.13(SIZE), BR (COLOR)
TRA_LPN TYPE SIZE COLOR
CIVUS-0.13-BR
AVS3.0G-B
AVSSH-2.0F-G
I have been doing an exercise to split the data from the list of the information into column A, B & C. Unfortunately the data value that i have consist of several set of data format therefore it create an issue for me to separate the information in Access 2010 easily.
eg.
Original Data Field FLRY-B-0.75-L-GY FLRY-4.0-V-R VTAC-GY 19X20 COT-F2-5-DL
Actual Data To Populate Into Column A, B & C should be the following :
I have a very large query that I need to export to text. I'm hitting the 4GB limit, so I'd like to "split" the query and create two text files instead.
What's the most efficient way to do this? Also, are there any export file formats that can handle more data? (i.e. is there a format that could fit this massive query into a single file?)
I have a table [Employees] that has the field [FirstName] and [LastName]. On my form [Jobs], I have a combobox [ComboWho]. The combo box has all of the possible first names. When a first name is picked, it makes the last name fill in a textbox.
In the real version, it is a [LastName] is a lot of information, so it is kept in a memo field. I tried to use cascading combo boxes, but it cuts off my text.
I keep getting it to almost work... I've tried about 5 different methods... DLookUp, subform, etc.
Right now, I'm using this code:
Private Sub ComboWho_Change() Dim location As String Me.ComboWho.SetFocus location = DLookup("LastName", "Employee", "FirstName = '" & Me.ComboWho.SelText & "'") Me.MyTextBox.SetFocus Me.MyTextBox.Text = location End Sub
It has properly filled in the textbox. I thought it was working perfectly, but ran into one snag... We have been using a split form... and it won't let me filter that column (Column ComboWho). I think because it is saving everything as numbers instead of text.
ComboWhoDatabase.accdbI've attached a copy of the simplified database.
I haven't done any testing yet on splitting the database I'm working on but a question came up today about networking.
This database is going to be used by a few equipment operators to record machine readings on the manufacturing floor. There is a wireless network and we are in the process of confirming that the wireless signal reaches all the areas. The users will be using ruggedized windows tablets to enter the data.
The BE of the split database will reside on a network drive to ensure everyone that needs it will have access and it will be regularly backed up. etc.
Since there is alot of heavy machinery, there may be some spots where connectivity will be weak or non-existent while they are entering their readings.
The question is how will the runtime FE handle it if connectivity is temporarily interrupted?
We have a split A2010 accdb, and the backend is now 1.8Gb so I need to do something If I put each of the 4 main tables in 4 separate backend accdbs, will the fact that the frontend then needs to link to 4 accdbs in some way impact on performance? Another possibility (given that 90% of our work only needs the recent data) is that I split the 4 main tables into 'archive' and 'current' (= recent) tables, with all the 'archive' tables in one accdb and all the 'current' tables in another accdb: but that would make it more difficult to run reports etc over the entire data Putting the 4 main tables in 4 separate backend accdbs seems like the answer to me - but are there any other considerations to this.
I'm nearly at the point of distributing my database. I have been writing this on my laptop and I need to get it working on a Terminal Server and Data Server at the data centre that host our system which is a remote location. The Terminal Server has Access Runtime only, not the full version of Access. This obviously presents me with a bit of a quandary as I still need to be able to maintain the software but do not want my laptop to link via the web to the database to do so. My solution is to take a copy of the database onto my laptop when I need to do anything, which is not a problem. My issue is that I'd like a simple way of maintaining the link between the Front end and the Back end so that if I upload a new copy of the back end or the front-end it will not throw the toys out the pram at the users!
I understand that I am best to put the back end onto the data server and to then distribute the front end to each user. Each user has their own account on the Terminal Server so I can put the front end into their userprofile or something similar (if it is true that I can't just give them all shortcuts to the same front-end that is?!).
I would like to try and get the back end to link to the front end via ODBC as if this is the case I can use the File DNS path on the terminal Server so each user has access and can use File DNS on my laptop when I need to do any updates on my copy so that I am not having to do anything too complicated with the linking of the front and back end due to the differing file systems. Is this possible to do or am I completely going at this the wrong way and missing an easier method?
i have created a database and just use the feature to split the database. i then set a password on the back end database. however now when i use a macro to open a form in the front end it won't open the form and just says incorrect password.
I tried saving my split database to a flash drive so I could move it to a computer that is connected to the shared server but it did not go as I planned. The back end with the tables works fine, but when I try to open the Form on the front end it says it cannot be located. I just want to take all the files I have (Should only be 2 front/back ends) and move them onto a new computer.
I am attempting to split an Access 2007 database. My company has two locations. From my location we are remote connecting into the server. While down there they are connecting directly. When I split the database, people in my location can use it fine. When people down there use it, they get a not valid path error.
This is because the network drives are mapped differently. I have been reading that the solution is to use the UNC for the back end file path.
I am new in database design . I did a database by access 2010 which contain form and tables and i want to split it to backend and frontend and then make then in website
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 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 have a split database with the backend on our server. When I go to my server and look at all the open files on the network everyone who is in the backend shows up twice. One has zero locks and the other has multiple locks.
For some reason when I change the order around of the columns in a split form or subform 90% of the time it wont save (right click save, file save, etc..) and have to constantly redo it until it finally works. Am I missing something obvious as to why this is happening?
I have a split database consisting of an ACCDB backend helf on a shared drive, and a local ACCDR frontend distributed through email. I recently distributed a copy of the ACCDR to a user, and she says that the main menu opens fine, but when she clicks a button to open a form, the form opens but is completely blank. I've googled some possible causes for this (e.g. on Allen Brown's website) and none seem to be relevant, or would explain why this started happening all of a sudden. I can't reproduce this bug at all.
I have split the database, with the back-end residing on the server. Only 1 other person is working in Access right now; she's verifying the data. Today she's working directly in the back-end, could this be the problem. If it is, I'm going to have to create a front-end for her quickly.
My problem is this...I'm working on queries and forms so that the scientists who will ultimately be using this application, won't be able to go in and inadvertently change something in the tables set-up. When I'm in the back-end main data table, it says I have 2723 records.
When I create a front-end query to query all the records in that table, it says I have 2160 records.
The input form that I created with most of the same fields as the query (created BEFORE I created the query...I'll have it pull from the query now instead of directly from the table) also says we only have 2160 records.
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?
Is there a tutorial on how to split a database so that it can be uploaded to a sharepoint site and one part of it allows updates and the other part only viewing?
