I am looking to upsize a Access BE database to SQL Server. The FE database will still be MS Access. I would like to keep the FE as it is and use an ODBC connection to the SQL BE database. My problem today is that I need better performance since we are using the database over a WLAN connection. As I understand it, Access sends the entire dataset/table across the connection whilst SQL Server only returns the requested data.
Is there anyone familiar with SQL Server that can guide me in the right direction here. Any insights are most welcome and appreciated.
TWe aare using computers with WinXP, server running Windows 2003 Server
Is there an easy fast way to do this: We are having problems upgrading to SQL server for only our backend tables. The problem is we have SQL reserved words that can only be used by SQL Server. There is a huge list I was given. I assume this applies to all objects, in our ms access database. Any suggestions on how to at least 'find' all of these at once? Or fix this easily? I know which tables would not upload ...but in looking through them I don't even see which reserved word is causing the issue???
Also..our front end application with stay Ms access 2003. Do I still need to update any reserved words in that or just the tables?
I have a dilema, my db is hosted on our shared drive, and with +-15 users at any given time there shouldn't be a problem. However, quite often the users get the message that they cant log on because the file is already in use. This will pose a bigger problem very soon, because there will be about 100 users total at any given time. My question is this; should I upsize or not? I haven't found much written on the subject, so I don't know if that would solve my problem or not. If it is a good idea, can someone tell me if it's possible with a split db? And since I'm new to this portion of Access, can anyone tell me what I should be aware of (unforseen brick walls). Any help would be greatly appreciated.
I have a VBA script that opens a intra net web page and downloads data from it. The data is stored locally in Access tables. After the tables are filled, the script ftp's the database to the web. This script is set to run every night at midnight and has worked well for months now.
I had to upgrade my website's database to MSSQL server from MS Access. So now my script needs to be modified. I need to take these access tables and upload them to SQL Server instead of a simple ftp upload.
In SQL management studio I can import an access database easily. It transfers all of the data in 5 minutes or so. But I have to do this manually and click through a wizard.
I have tried setting up linked SQL tables and running append queries with VBA using DoCmd.RunSQL This method is way too slow. I tried saved append queries using query design grid and it is only a little faster.
I am transferring 10 tables or so, with anywhere from 1000-100,000 records. I've read through 3 pages of SQL Server searches and I am still at a loss. I really need to automate this process.
I've always practiced to keep my backend table names to no more than 8 characters because of speed issues. Can this also goes for the server name? My current location looks like this now orld71-testing-aFinance..I am wondering if changing the server name with speed or is that only for folder names.
Hi. Your help is very appreciated. I want to upsize large MS ACCESS(2002) app to MS SQL SERVER 2000. [ By "large", I mean 250 queries, 78 tables, 110 forms]. The app will be used by 25 concurrent users.(therefore the need to upsize).
I have time constraints of 2 weeks to deliver.
My questions:
1. In order to finish it asap, upsizing ONLY the tables - might be a good solution. However, will it work with a workload of 25 concurrent users?(read/write).
2. If upsizing all the tables, would it be possible to upsize SOME of the queries and leave the rest untouched? If yes, what is the process to do it? That will save me lots of QA time (there are 250 queries). Mind you it's not simple, since the forms need to reference Stored Procs as well as ACCESS' SQL queries.
3. In the upsizing documentation, it says that there might be situation that the query will be upsized , no errors will appear in the log BUT it won't work anymore :mad: . Do you have any methodology for QA the upszied queries in order to ensure the system's robustness?
I have an MS-SQL backend which i use for my data source. I then use Access for reporting services. (It works so much better than SQL Reporting Services 2005).
this seems simple, but i can't get it to work. Everytime the users start up access, It pops up a login and password for the ODBC link. Even when i have the password and login setup in the ODBC DSN, it still requests it everytime you start connecting to the datasource.
Is there anyway to somehow hard code this into the Access front end somehow so i don't have to give the password to the users?
I'm currently researching on how to best migrate from Access back-end to a SQL backend, and was able to find wealth of information on how well Access can play with various SQL servers, how ODBC drivers are implemented, and how JET handles queries to backend. If this helps matter, I'm considering using MySQL as a backend.
That said, there are some gaps in my research that I'm hope someone will be able to fill in for me.
1) I have couple of queries that may use Access's custom function not otherwise supported in SQL servers. If I based the query on otherwise executable query, would JET be able to pass the sub query to SQL, and get the recordset and apply the next query using custom functions without any problems?
2) In general, DAO is best when you're using JET, but ADO is best for ODBC. I'm not clear whether it's possible to use a mixture of ADO and DAO, provided I've disambiguated the library (which I already did anyway) to make even efficient use of recordset. For example, I'd use ADO to work with data from backend and once it's bought over here, switch to DAO for faster handling by JET. Is that possible *and* advisable?
3) I found lists about limitations or problems that may arise due to differences between Access and SQL, which is good to know. However, I never found any answer as whether VBA may cause problems with using SQL data. Let's say I have a form that has lot of VBA coding to handle calculations, multiple selection in listbox to be added to a junction table, dynamically changing rowsource for a combobox, whatever that is based on a query that otherwise runs fine with SQL server- will the form still work just as fine or are there going to be any surprises after migrations?
4) Somehow related, if this is supported by whatever SQL server I may use, would I be better advised to use stored procedures in place of VBA for Access forms?
I have two laptop computers. Both have Access 2010 installed. Both computers are on the same Workgroup and each computer can access files on the other. Computers are connected with wireless connection. Computer 1 holds the backend data while computer 2 is used for data entry and connects to backend on computer 1.Both computers are used for data entry, and as I said, data is stored on computer 1 only.
Here's the problem. If I enter data on computers 1 and then open computer 2 I cannot access the data unless computer 1 exits and then reopens. If computer 1 does not exit and reopen I cannot access the data from computer 2. In addition, if I enter data in Computer 2 and save it then computer 1 can see the data and all is well. So, for everything to work I have to start the data entry in computer 2. If I start data entry with computer 1 then I have to go through the save and shutdown process.
I have tried requery and refresh, refreshpage, refreshrecord, etc, but with no success.
Im totally new at all this stuff, so any help is appreciated.
i have a database with one table that has many different attributes and almost 3000 records. this is all i have done, i have simply been loading in all of the data to the table, now that that is done i need to allow users to extract the data.
so, what is the best way to build a front end that allows the user to easily extract data from the database? ideally, i would like to have some sort of front end that would have a text input window where they could search for records matching attributes in the table that match or are close to the text they type in, with some additional options for honing down the search terms with dropdown menus, radio buttons, etc.
the problem is i really havent a clue on how to do that stuff. can anyone just give some general, beginner type steps for things i should be doing to create that "front end" i am visualizing. THANKS!
On my development machine everything works great, but I know that I'm going to run into problems with distribution.
I don't think there is a way, but I'll ask. Is there any way to get around not having to install the ODBC MySQL drivers on each computer? One of the reasons I'm migrating to MySQL for a backend is the fact that I'll be going from 10 users to 150 users, each of which has a "locked down" PC, which would mean logging into each with Admin rights to install the driver. Not an impossible task, but a pain.
Is is possible to have a "shared" source for the driver? I have only a rudimentary understanding of that process.
Thanks in advance for any help that someone can provide, or some answers pointing me in the right direction.
I am evaluating a program for the use of a customer. It's a VB frontend attached to an Access database.
The backend has no relationships. No table in the backend even has a primary key.
My question: Is this scenario acceptable in any way?
I tend to think not, but am unsure whether the design of the frontend application establishes relationships "on the fly". Even if so, the fact that there are no primary keys makes me think I should dismiss this application out of hand.
I am very good at excel and can program macros. I am being asked to build something in access for my company, or at least manage a build. So here is my question... If we build it without both a front and back end, is it easier to take what you have and switch it to a front and back end? Also, when and why is it better?
I have an ACCESS 2003 application with front end in the local machine and backend on the shared network drive. I mapped this drive to E: in my computer and all my linked tables show the E:folernameDatabasename.mdb as the source.
When I install this application in an other computer where they have mapped the same drive to F: , I am getting error that says "E:foldernameDatabasename.mdb" not found. How can use absolute network drive(like \cscrd eamfoldernamedatabasename.mdb) name to link the tables?
I want to deploy an access database at a small office with 5 computers, small network. However I do not intend to create a server in order to have a domain etc. Operating system is win 8.1 pro. Should I use a homegroup or workgroup ? Would it require password in case of workgroup? Which is a recommended way to setup this and keep some security like a guest cant access these files?
I have to use MS Access as front end with ODBC connection to Oracle 9i
DB.
The application(forms) should be able to update, delete ,insert records into oracle tables(backend).
i have a main form,which has some unique id's and other info about the ids and the subform shows several matching id's for that unique id in main form. the user who uses this application should be able to 1) search for the unique id in the main form such that the subform displays all its matches 2) they should be able to select anyone match and say approve(there can only be one match), then that particular record should be updated in the table.IF I USE A CHECK BOX AND IF THEY CLICK ON ONE RECORD AS MATCH,HOW DO I TAKE THAT RECORD SAY THE ID , NAME ADDRESS AND ALL DETAILS AND UPDATE THE TABLE??? similarly when they select some other record i should give option of deleting other irrelevant matches in the backend table.
the main form and the subform uses the same table as source.updates are to another table, i should also have to put entry into audit table about which record was deleted and which one inserted..
How should i do this?? i am new to MS access .VBA, any help would be highly appreciated!
If I want to distribute a front end to connect with a MySQL back end ... do I need to set up the system DSN on each workstation that will be using the front end?
If I have an MS Access frontend that connects to an MS Access backend, is there a way to hide/permission block the pathway to the backend's folder but still allow access via the frontend db?
Right now I can't dedicate a server to a more "secure" form of DB or anything like that so I'm stuck with MS Access for now. I just don't want someone looking at, say, a link table path and then navigating to that folder and getting access to backend information.
We're currently looking at changing a couple of my more complex Access 2003 databases to Access Front End with a SQL Server Back End. This should give us better stability and reduce network traffic loads. I was looking at the Access help file on Upsizing and came across the following paragraph. On face value to a novice like me this would seem the easy option - but is it?
"Create an Access database front-end to an SQL Server database back-end so that you can create a front-end/back-end application.
This approach requires very little application modification since the code is still using the Jet database engine. "
I am importing an Excel file into a table in SQL Server that was created by an AS400 program.
I linked this table in MS Access. The date fields from the SQL Server table are split out. DSREQM is the month and day. DSREQY is the year. When opening the table it looks like this:
DSREQM DSREQY 215 6
I need to be able to convert this is a field to 2/15/06. However I cannot get this to work. For some reason when I execute the query it comes out as 8/02. Here is what I have:
I am attempting to write an application, using Access2003 as the front end. The Backend May be either Jet (ie an MDB), or SQL Server.
I am trying to make it so that the same code works regardless of the back end.
My approach has been to set the forms recordset to an ADO recordset like so:
Set Rs = New ADODB.Recordset 'Rs.CursorLocation = adUseClient Rs.CursorLocation = adUseServer Rs.Open strSQL, gcn, adOpenDynamic, adLockOptimistic ' Set Me.Recordset = Rs
Anyone done this, and willing to sahre information/pitfalls.
First problem I am encountering is that Jet only seems to like .CursorLocation = adUseClient, and SQL Server only seemns to like .CursorLocation = adUseServer
I just "upsized" an mdb front and back end SQL Server Express using the upsize wizard.
I have a sub-form with a list box that does not seem to work. Here is the recordsource:
SELECT tblProjectSegment.strSourceCodeID, tblProjectSegment.strEventCodeID, tblProjectSegment.lngProjectCodeID, tblProjectSegment.SourceCodeLink, tblProjectSegment.strStatusID FROM tblProjectSegment WHERE (((tblProjectSegment.lngProjectCodeID)=[Forms]![frm_ProjectData]![frmSourceCodeInfo].[Form]![lngProjectCodeID]) AND (Not (tblProjectSegment.strStatusID)="utad")) ORDER BY tblProjectSegment.strSourceCodeID;
