Can anyone direct me to someone that does work with Office 2000 Developer
to complete a database runtime version. I paid Microsoft for help that was expensive and all i got was suggestions to but more software. I own Office 2000 Developer 2000 version 1.5. Its a small job so I dont know where to start looking for someone to hire.
Thanks
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.
My database is written in Access 97 (I know get out of the stone age) but we have a mix of office 97 and office 2003 users. Anyway I'm afraid that one of the few people that have access 2000 or higher will open my database and convert it. I found (through here) code to check the version but it is attached to a form opening which is way to late. Is there a way to have access check the version as soon as you click to open the database and if it isn't 97 close the database?
I've been having serious problems with my ASP scripts. Ok, for the last week or so I’ve been working with you people and my ISP to resolve this damn problem. Just last Monday, they told me that it had been fixed. And it was true! I tried it and everything once again worked fine. I made a dozen tests, and everything worked fine. But when I tried it again two days later, it's suddenly back to crashing again, the exact same damn problem I was having before! I’m so frustrated I could kill. I don’t think I did anything. Yes, my ASP code still works. Yes, the HTML code still works. It’s when the code attempts to open a *.mdb database it crashes.
Call up my demo script (then click "Reservation.") : http://christiansencustomsoftware.com/guestbk/dindex.htm which will demonstrate the problem.
A newsgroup I work with writes: “This sometimes happens when you try to use the new MS Jet provider on a Access 97 database, upgrade your Access database to 2000, should work just fine.”
Ok, so how can I upgrade my Access database to 2000?
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?
I've been having some problems with sharing an MS Access 2000 database across a network.
The database is setup to open in shared mode and has been tried both with and without record locking, with the same issue occurring.
The main users are: User 1 (Administrator) - MS Access 2000 Full Version (WinXP Professional) User 2 - Access 2000 Runtime + Access 97 (Win XP Professional) User 3 - Access 2000 Runtime + Access 97 (Win XP Professional)
The problem is occurring when User 3 opens the database. For some reason it opens in exclusive mode and locks out Users 1 & 2. This issue only happens with User 3, and does not happen with User 2 who has the same software setup.
The database was previously an Access 97 database (no problems) and has been converted to Access 2000, this share issue has been happening ever since the conversion.
Any ideas as to how this shared issue could be resolved? :confused:
BTW - I am familiar with FE/BE setups. This database is accessed by all from a network drive and not setup as FE/BE. This was never an issue, as shared access worked fine when the database was in Access 97 - the problem has only been since converting to Access 2000. I do not have access to the PC of User 2, and User 2 does not have any PC knowledge to install a FE, which means I would need to create an install package (which I'd rather not do). Are there any ways to resolve the shared access issue without changing to FE/BE?
I've installed the windows XP. Also, I have an ODBC connection to ACCESS 2000 database. My scripts are already reads data from ACCESS databse. But it is failed to create new table in database. What may this problem be solved?
I am doing some computer work for a company that has an Access 2000 application. This app is split up between a program database that contains the forms, reports, etc. and a data database. Both the program database and the data database are located on a Windows 2003 teminal server. There are usually two or three remote users logged into the terminal server, but this number is about to increase to 6 or 7. I am concerned that these user's will all be running the same copy of the program database. I have read that this can lead to performance problems.
I was wondering if anyone hear thought either of the following would be an improvement:
1. Put a separate copy of the program database in each user's profile on the terminal server.
2. Rather than keeping the program database on the terminal server, put a copy of it on each of the remote client pc's. Then set up a VPN connection to the server and use this to link to the data database.
If anyone could tell me if either of these options would lead to improved performance, I would really appreciate it.
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 am trying to creat a booking system for cars which has a specification of being able to be hired by the 'week'. I am thinking of creating a table with every week date (every monday) from Feb 28 2005. Just wondering how I would create a table do to this with an append query?
I was thinking something like looping from Feb 28 2005 (monday) and dateadd + 7 a few hundred times then having an HireID field in the same table and once a car is booked for a one week period its start date hireID (or CarID) are entered into the database so nothing can be double booked.. I am just not so sure how I would reuse each date for all the different cars?
I have been creating a Access database to hire bikes out. I have created all the tables etc but i am stuck creating a query i want to create. I want to have a sub form on my booking form from a query which will show all the available bikes that can be hired. I have looked at the lending library sample and this hasn't really worked, My database is set out differently.
I have attached a version of the database to the post, this is zipped with some screenshots which may be useful.
I built a ms database and I'm just wondeirng about the compatability of using 2007, what kind of issues can i expect to run into and does this sound like there will be a major overhaul needed in the programing, or should it be pretty straight forward.
Hello I have one question I have simple table in Access 2003 with three fields One is (field name), type - autonumber one is (field name), type - number one is (field name), type - text
my problem is that i need in number field nubers between1 and 2000 and in text fields same numbers between 1 and 2000 with letter G at the end.
that will look like Autonumber 1 ... 574 ... 2000 Number 1 ... 574 ... 2000 Text 1G ... 574G ... 2000G
Problem is that I dont know how to write a code for that i think that there would be a macro. So can someone help me please!
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!