I have been using front-end back-end database, which consists of three .mde files connected to an .mdb backend on a Windows Server 2003 Windows XP Professional network. The database is a flat-file. Because of problems associated with record corruption, related to multiple users and memo fields, I am looking to upsize my backend to MySQL or SQL Server both of which I know little about. Additionally I am hoping that upsizing will help alleviate the slowing down I am currently experiencing as the back end grows.
My question is am I looking in the right direction will either of these correct my problems and if so which of the two should I use.
I'm just after getting my web site designed and I want upsize my present database which is MS Access to a MSSQL server can anyone help? I'm totally new to databases so I need step by step help!
*I upsized ACCESS 2002 (tables only) to use SQL SERVER 7.0 as backend. (linked tables). * Almost all the ACCESS forms are bound type forms.
Now, I have two problems: 1. Other applications (not ACCESS ones) that use different dbs on the same SQL SERVER , are slowed down / halted. 2. My SQL SERVER license is limited to 8 "user counts". When there are 8 instances of the ACCESS app, any additional connection request is refused (from any app). (I can't afford buying more "user counts").
I suspect that beacuse the forms are bound, it hold connection open as long as the form is used. Also, each ACCESS app instance, opens its own connection.
The solution that I see, is to use unbound forms(disconnected), and opening the connection in code using connection pooling. Would you recommend on this solution? do you have any suggestions?
I am trying to upsize the access database to sql server ,i have an odbc connection and when I try to move the tables,all the data is moving except one table "tblproductinfo" . I have attached the table data and error.
I have upsized from Access 2003 to SQL Server 2008 R2 using upsizing wizard. Everything works fine. But I don't see relationship in SQL SErver 2008 R2 if I go to database. But I set relationship in Access 2003 before upsizing it.
Amso I don't see relationship (diagram) in Access 2003 , which I was able to see before.
So do I need to again recreate the relationship amongst the table in Access 2003 Or SQL SErver 2008 R2 ? I thought, if you link tables, everything should be taken care but i don't see relationship structure any more.
I have a MS Access 2003 database that is getting corrupted frequently. I am following all the rules to avoid this problem but it keeps boring me with "Access can´t recognize this database format" and I lose all my data. I´ve sent the db to experts to try to recover it and they told me that it was impossible. So, I´m planning to change my Backend (BE) and keep my Access Frontend (FE), because I like Access very much. My question: what is the best solution for BE? SQL Server? Firebird? another one? I hope by changing the BE I won´t have problems anymore... Thanks in advance Renato
Would anyone be willing to have a discussion about upsizing a large split database to SQL? I've managed the split using the wizard and it went very well. The problem is the performance, the form is really slow on opening and as it scrolls through records.
All my queries are saved. I would imagine it's the way I've built the form and base queries that's causing the problem and wondered if anyone would be willing to have a look at it for me and see if they can make any suggestions.
It's much as I thought it would be. MS Access is limited for a mid size database application. I have developed this mid size database for the medical clinic I work for. I didn't want to do it, but they saw some of my personal projects I created and pretty much told me to come up with something.
Well, the good news is, the database itself works exactly as designed, meaning it does its job very well. The bad news, and I knew it would happen, is instability. When I first started creating this program, I had no idea how many people would be using it at once. That, and after reading through these forums for the last few months, I realized that Access wasn't the puppy to be creating this database in. As it stands, about 130 - 150 systems access the database (about 3 times more than I originally forcasted.)
I'm sure those of you who have done something similar knows the next thing I'm about to say...... yep..... mysterious run-time errors - locked database from time to time - owc (office web component) errors...... etc. etc. These errors pretty much happen during peak hours.
I am pretty positive it's because access wasn't designed to handle such a load..... which led me to a researching a resolution. The answer that may be my savior is the upsizing wizard included with ms access. We do have MS SQL server running on a server...... I was just curious if anybody's ever used the upsizing wizard; either that, or has anyone ported an access project to sql. (This is a big program, and would hate to have to reprogram)
I have developed a couple of database applications. This started as a small thing but now is growing to the point where I've got to make some decisions and would appreciate some guidance.
Presently:
Front end: 4 Different GUI's as local front ends. Back end: Intranet network share on Win2k desktop (limited by O/S to 10 connections at one time)
Going forward, about 30 users will have access to the front ends and will all need concurrent access to the back end data. At some point, I would like to generate web pages from the data in the back end database and have the back end machine also be the web server for this.
So, what are my "best" options for the back end? I was thinking of getting Win 2k3 Server running SQL server to drive the database.
The ability to integrate security with existing infrastructure would definitely be a plus, which I believe Win 2k3 can do.
I don't know very much about Win 2k3 or SQL server, but am willing to invest in learning the ins and outs as long as I can get it up and running with the same functionality I have now (with relative ease) and scale it as my capabilities with the OS and SQL server increase.
To be honest though, I am a little scared about how much I'll have to change my existing applications in order to make it work.
Your suggestions, comments, experiences most welcome and valued.
I am upgrading a .mdb to MSSQL. The .mdb is 17MB, but the resulting MSSQL is 72MB. Tried using both the Access Upsizing Wizard and Enterprise Manager DTS. I have done this a number of times before, but never ran into this problem. Any ideas what coule be going on, and how to fix it?
I have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard. But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007. I can't use the Package Wizard.
Hi, I have been using "fSetAccessWindow (SW_HIDDEN)" in the open event of my main switchboard to hide the grey Access screen from being visible behind forms, reports, etc in this db. But when I started using a .vbs script file to launch the db, the Access window stopped being hidden. (The reason I use the script for launching is that it temporarily sets the db's security level to 1 which stops the macro security warning from coming up.) Apparently MS knows about this happening and released a technique to rectify the situation, but I don't understand their instructions. It looks like they expect one to have more understanding than I have. Could someone help me get this impliemented? Here is the article: http://support.microsoft.com/kb/167659/en-us Thanks!
Hi! This is Kishore, working on VB Project which is using MS-Access95 as backend. Now, i want to change the Database login Password. Could anyone guide me in this context.
Using Access's User and Group Accounts or Using a Login Form to access database?
I've been researching on how to make a database secure. How to create User and Group Accounts on access, I see the step by step instructions and tried it out myself.
I also saw some sites where they give an example of a Login Form and how to create one.
My question is do you need to create both. First create the users and groups to permit or deny access to certain forms and then have a login form?
But would that mean that they'd have to login twice? Once when the database opens because it activates the db security that was created and then login again in the login form that was created?
Also when the user logins in and clicks on the cmd button on the form which opens up another from, frmWorkLog, I have an Employee field. This field I want it to have the user's name entered automatically and "locked". So that info, employee name, is extracted from the user's login. So then the user can only see his or her records only and no one elses.
How would I go about creating that. Hope I made my explanation clear.
I have two database applications and they are: - the (A) application is for administration use. - the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I have a simple access search form , that's based on a query that fill parameters from the form textboxes, when the access form loads its keeps prompting for parameters value which looks ugly .. I want to open the form, displaying all the records in the table and filter when i click search ..
I have a data entry entry form, that i want to generate success message after successful insert in database. I have done it in the button event if no error happens, still if i left all fields blank and clicked save, it displays the message ..
I need to change that to display please fill the textboxes then click save , and display success message when the row is actually inserted ..
I've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables Dim db As DAO.Database Dim qdf As DAO.QueryDef Dim varItem As Variant Dim strCriteria As String Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM qryContractListSummarybyDateContract3TYPEBREAK WHERE qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri Masonry NSW');'
Attached is a screenshot of the relationships in a database I built a couple of years ago. It's worked absolutely fine in Access 2003 and currently has over 18,000 customers with associated information in it.
However, when I open the database in Access 2007 the performance is awful. All the forms are very slow to respond when tabbing between form elements. I've experimented by reducing the number of form elements calling on related data on a given page and whilst this improves performance it reduces usability - something I don't want to compromise on especially since Access 2007 should be able to cope with this.
My next question is therefore whether I've got the most efficient underlying table design and I can't see any other way of doing it than my current method so I'd be grateful for any feedback or advice anyone has.
I have a stock control database which i have nearly completed. This has Manufacturer, which is linked to products, which is linked to Sub Product(which also has field partCode). i.e. Manufacturer1 can have 3 products, and each of these products could have 5 subsystems and partcodes. Each partcode is unique to that subsystem/product/manufacturer.
I then have a pricing spreadsheet in excel, which has many tabs. A new column has been added for each item for Manufacturer,Product,Subsystem and Partcode.
I need to import these manufacturers,products,subsystems and partcodes, but into the tables with the correct relationships, i.e. product1 and product2 are products of manufacturer1 and so cannot come under manufacturer2, and so on.
I hope this makes sense, Thanks in advance for any help you can give!
I am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
I have made a form on access which will be used by other employees within the company, however they have never used access before and they are wanting to access only just the form as I feel with Access and all the tools in the background will confuse them, plus I don't want them editing the data base its self.
Is there a way to only bring up the form, unless I obviously need to edit the date base.
I've done some research on Google and it seems I need to use:
SW_SHOWMINNOACTIVE
However I can not seem to find how I would use this or where?
and also if i did find a way to only bring up the form, how would I be able to switch it from that veiw to the veiw I edit in?
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks. Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset Dim ObjXLApp As New Excel.Application Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer Dim TotalBlank As Integer, R As Integer, C As Integer Dim BadSheet As Boolean, ImpFail As Boolean Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then MsgBox ("You must select a Program to load.") ObjXLApp.Quit 'Exit from MS Excel Exit Function End If
I have an Access DB that I created in Access XP. It works perfectly when used in Access XP. When used in an Access 2003 environment some of the functions don't work anymore. I have users who use Office XP and users who use Office 2003. Does anybody know how to make this DB work in Access 2003 without having to do wholesale code changes?
I have already changed the security to "Low" to bypass the security feature built in in Jet 4.0 but it didn't help. I might have to uninstall Windows XP SP2 to make it work because I know that the application works in an Office 2003 environment with Windows XP SP1 only. But I'm trying to avoid having to uninstall XP SP2 because it's a pain. Any ideas would be greatly appreciated.
Thank you.
My workstation environment is as follows:
OS: Windows XP SP2 Office: Office 2003 SP1 Jet: 4.0
