I have few problem with my current Access 2000 application.
I create blank, new Access 2000 and import all objects from my Access 97 instead of going thru conversion process. I have several problems with my current 2000 version. I am new to Access 2000. I'd appreciate any help...
1/ The application once in a while have message "The database is read-only. You can't make any changes to the data-definition of the databases..." when I open it occasionally. Then I can not update or add anything. How do I prevent it from happening??
2/ In Access 2000 all my reports format changed to "portrait" orientation and the margin. So I open exclusively, even after I spent time to change to "landscape" and the margin I desired, saved it . Next time I open, some reports format saved, some change back to "portrait" and margin is 1''. Why don't they saved??
3/ My application is on the network server for multiuser environment. Everytime I click design view of forms, it has message saying "You don't have exclusively open..., so your designed changes may not be saved..." but in Access 97 is OK. How do I turn off that feature?
I've got a fairly complex access 2000 database that's split into front and back ends.
There's 32 back end tables and a whole host of complex front end queries and forms. The whole thing's around 25,000 lines of code so not a 5 minute job to rebuild! (sorry but i just can't stop tweaking it!!)
I hate the idea of all that data moving across the network, and having to make the front end machines work so hard so I'd like to get the server doing it's fair share of work because it's got dual 3Ghz Xeon processors which aren't earning their keep! I was thinking about converting the mdb to SQL and although i could pay someone to do it for me, i do like to learn! (so when it breaks i'm not at anyone's mercy!!)
I assume there isn't an upsizing tool on the planet that will let me do this by clicking a button so can anyone point me in the right direction with regard to something decent that can automate as much as possible. PLUS a good source of information on the differentces between access and SQL so that i can start seeing how to accomplish with SQL what i'd do in Access?
I just upgrades from Access 2000 to 2003 assuming that once I converted my old database, I would get the new style command buttons... is there anything I can do to get them to work?
I have a database that currently has security in place so that users input their own usernames and passwords to access the database. The users have recently been added to a windows 2000 server and I want to be able to use their windows 2000 server logon credentials to provide them with automatic access to the database. Is there anyone out there who knows how to set this up? It is a rather urgent request if you could get back to me either on this forum or via email
I am opening and closing a series of Excel 2000 Workbooks using Access 2000 VBA and want this sequence to be able to complete without any human intervention.
However, there are 2 instances when this stops and waits for a human option to be selected:
1. When the spreadsheet is password protected 2. When the spreadsheet has automatic links I get the message:
"The Workbook you opened contains automatic links to information in another workbook. Do you want to update this workbook with changes made to the other workbook?"
How can I code it so that in situation 1 it skips this file and in situation 2 it automatically defaults to do not update?
If I have a report in MS Access 2000 generated based on the criteria selected of a project with work order "9999" with the labor costs, materials costs and the Totals of each crew1, crew2,... and I would like to have those expenditures populated in corresponding cel in Excel for each crew, HOW would I do it?
To think it out loud, could I create a button on a form, so when I select the criteria for the work order, and when I click the button, it should refresh/update the Exel file with the new data...?? How do I write VBA code for that...?
I have recently been doing a conversion for my boss for a access 2000 database (both front and backend) to a MSSQL backend.
I finished the conversion today (as quite a lot of the code / queries ran slow due to access running the queries locally rather than on the server). And tested it on my and my boss's machine with no problems so he gave the go ahead to update everybody to our new mssql 2000 backend with the modified frontend.
This is when the problems started; We had two different sets of forms for accessing one of our databases systems - the log system, one is the original dynaset based form, and the other is a newer set which uses snapshot views and preforms updates via queries. Nobody uses the old dyanset system apart from my boss and one of the administrative team as they have things on that window which they need to see. About 30 minutes into the release of the new database the system frooze up on my bosses computer and nobody could create a new log (the server was timing out). I assumed this had something to do with the old dynaset's creating locks on the table.
I offlined the database and kicked everybody out of the front end, turned it on again and tied again, this time banning everybody from the dynaset system. Within 10 minutes another computer frooze up, again with a timeout on the insert query. I discovered that after you had added a new log to the database it would timeout on all subquent additions (something it hadn't done during testing) . Further investigatiion showed it was the snapshot list window causing the error, so coded the add log window to close the list before preforming the insert query and then reopen it afterwards. This allowed my machine to make multible additions without flaw. So I released a new client to everybody. 15 minutes later it was timing out again, but this time there you could not even make one new record.
I checked for locks on the table though the server management table and couldn't find any for the Log table. I have restarted the SQL server box and with no avil. So I reverted our backend to the access mdb file and told people to use the old client.
I am at a complete lose to why this is happening, if anybody has had any expericences like this or knows the cause please tell me.
Some information on the database in question.
It was made as an access 2 database all intergrated into one file, then it was seperated into two files (frontend and backend). Upgraded to Access 97, then to 2000 before this final update to MSSQL 2000.
The log system has two main tables. The first is the log title / info table which links (one to many) to a log entry table. This problem only occurs on the main log table and does not appear to be reoccurring anywhere else within the database. The main log table has just under 18,000 rows in it.
I have been tasked with updating an Access 97 database with several forms that would take me a good while to recreate.
I wondering if there is a way to convert them from 97 to either VB6 of VB.NET that is free of charge to me. All the solutions I have come across thus far cost money, and it is not possible for me to do this.
I have tried exporting the forms to an external file but it won't let me save them as a file type that my VB6 installation can open.
Considering the difficulties in packaging Access software, I am wondering about the feasibility of converting my Access project to VB and distributing that instead. Has anyone done this and if so how difficult would it be. Does it mean a complete rewrite or can I use existing forms, reports and coding etc.
I have an Access 97 database that I’ve converted to Access XP. The font end database is on each user’s computer and the backend is on a network server. The database is updated with data from a mainframe db2 databases. I have 87 queries that pull the data from the db2 data base and import the data into an Access database that resides on a net work server. All these 87 queries are append and update queries that clean up the data and set it up in Access.
In the Access 97 database it takes 9 minutes to run all these updates but in the Access XP database is takes about 32 minutes. Both the front end database and network database are converted to XP. I have found that if you link a 97 table to an Access XP database, you slow everything down in the XP database ???, so I’ve made sure that all linked tables are XP. I’ve looked at my queries and tried to optimize as much as I can but nothing has worked.
I have several parameter queries that really seems to run extremely slow. I’m updating fields in on table with data from a field in another table. I using the query execute method with a loop to set the parameter each time and then execute the query This works well in 97 but in XP it’s extremely slow. I’ve changes indexes in the tables and at one point and at one point removed all indexes except for the index on the joining fields in the table.
All of the forms and reports in the database also run much slower.
My company has also upgraded. When I was using the 97 database I was using windows NT. With the XP database I’m using Windows XP.
If anyone has any advice or ideas, I would appreciate hearing from you.
If a company has a hundreds of databases and they want to know which databases have conversin issues such as DAO to ADO conversion because Modules and codes behind the forms refers to DAO code and not to ADO. Is there any tool which can tell this or some other ideas?
What I have now is an excel template (with ~12 worksheets) that many regional offices use to enter in some lease data, from which the excel sheet creates a rental schedule and does a whole ton of calculations on that data. Some are NPV calculations, some are yields etc etc.Eventually, I would like to:
1) Enable users to fill out one of these templates, and save the data to the database (Just the inputs? All the data? My reading suggests just the inputs) 2) Use the database to produce one of these templates for any lease in our system (shouldn't be hard, from what I've read) 3) Sum up calculations from this template for many records (eg. if a tenant has many leases, what is the NPV of all of those leases, or what is the total NPV for all tenants)
I have the inputs (from Access) I will have no problem using them in the excel version, but does it make sense to use Access given that I may need to somehow be switching back and forth to get the info I want for my various reports? I am very comfortable writing macros in VBA for excel, so if that's the solution, that is no problem. I assume what I need for #1 and #2 is a macro to arrange the inputs from the excel sheet into a format that can easily be dropped into access tables and vice versa.
Is there any way of converting MS Access Forms(And module behind) to Visual Studio.Net?
I have a pretty comprehensive MS Access DB that has several complex forms. I want to redo this DB App in Visual Studio.Net but don't want to recreate the forms from scratch if there is any way of converting/importing or any shortcuts/tricks to accomplish this.
Thanks in advance for any help!
Mitch
Side note: Anyone ever added credit card billing capabilities to their db? Where to start? (I know.... Post in another thread....)
Hello, I have getting type conversion errors for numeric and currency fields when importing an Ecxel spreadsheet into a Table in Access. I have tried changing the data type to text in Excel, and that is what it says I have done when I examine the field formats in question. How can I force this to be text, it keeps reverting, i.e. the fields in question, to numeric and currency. Can anyone help? Thank you. Joe
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 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 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've created a database in access 2003 with the default file format being Access 2000. Everything works fine on my computer and many others, all of whom are running different versions of access (2000, 2002 & 2003).
I have not had any problems with this database until recently and in the last few weeks we have had 2 users, both of them being Access 2000 users who have had the same problem.
The problem they are having is that when they click on any of the switchboard items, the buttons depress an then come back up again when the cursor is moved away, but nothing else happens - no action, no error message - nothing!!! Its the same for all of the buttons on the switchboard.
Does anyone know what is causing this? I have another computer with Access 2000 on it and this works fine, as it does on several other computers runiing Access 2000, I just cannot understand why it is not working on these 2 particular machine.......
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
We have two computers in a work group. On computer1 I have the back-end and front-end database files in the shared folder and 2 users out of 4 can access the database no problem. When the other users try to access the database they receive the error message "Microsoft Access can't Find The Database 'C:Documents and SettingsAll UsersDocumentsdb.mdb' Make sure you entered the correct path and filename" On computer2 I have the front-end database files in the shared folder and pointing to the same back-end database on computer1. Again 2 users out of 4 can access the database no problem. When the other users try to access the database they receive the same error described above.
I expect that this is some sort of windows permissions issue? There are some clues to this fact .. The two users that can't access the database are limited accounts, but I tried making them administrators and this had no affect. Their shared documents folder does not have a hand underneath it?
Any help on this appreciated as it's really starting to annoy me now!
A few years ago I’ve made an access database on access 2000. The problem is that now I’ve installed the office 2003, and I can’t make the database work properly.
At first says that are missing those files: “tshoot.ocx”, “msioff9.ocx” and “msowc.dll”; so, I’ve copy them from another computer using office 2000 and now only complains about “msioff9.ocx” saying that my database contains a reference incomplete to it.
Is there no other way to convert my database do work properly with access 2003? What can I do?
The company I am consulting with uses Access 2000 and has no intentions of upgrading. I currently do not own Access on my laptop.
I was planning to purchase Access 2003 for my laptop but am concerned that files I create in 2003 might not be "editable" in 2000 even if I choose the 2000 format when creating new databases.
I'm just wondering if anyone has tried creating a file in 2003 (using the 2000 format - as I'm told you can choose what format you want to use) and then edited it in 2000. I want my client to be able to edit the files in 2000 once I've moved on. (I can get 2003 for about the same price as 2000 - so my preference would be to get 2003.) The other obvious reason for going for 2003 is that I could run into the reverse challenge if I own 2000 and my next client uses 2003. At that point, I'd be forced to upgrade to 2003.
My databases are not complex - but do include some customized macros.
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
