I am pretty new to Access, so please bear with me :rolleyes:
We have a paradox v 3.1 database that I somehow converted into Access. At least the data was transfered and I can update it via a query.
What I am having a problem understanding is the difference between the main database file (in the object viewer appears as a db, with the the tables underneath. Am I correct to assume that all of the information is centralized into this db file?
I'm also having a problem changing the field lengths. I get a message "table "name" is a linked table with some properties that can't be modified."
I'm assuming this linkage came from paradox, because I didn't do a darn thing to it!! Any ideas on how to "unlink" would be greatly appreciated.
I have converted desktop Access database to SQL server. A medium sized app with 24 tables, 60 or so forms/subforms and about 120 queries. I created 2 split files, one containing the tables, and the other containing forms, queries, vba modules. I migrated the tables to SQL server using SSMA, and built an odbc connection for my front end. It works, except it is painfully slow. Its cos most of the recordsets that drive my front end are query based. And in many instances the queries are comprised of queries, not just tables.
Should i be creating my queries on the SQL server? Is that what people do when using Access front end with SQL server back end? Do away with Access queries? Or does the problem lie elsewhere? How do i network optimise my Access FE / SQL server BE?
I have an access dbase trying to link a paradox table. I have Office 2003 and BDE 5.01 was installed on my machine. When I try to link to a paradox table its giving me an error "Unexpected Error from xternal database driver (11265)". On the other hand, I have Office XP on my laptop and BDE 5.01 installed, I tried to link to a paradox table and it works. :eek: :confused: What can I do to link to a paradox table using Office 2003? :confused:
I have been given a paradox .DB file that I can (seemingly) "import" to Access 2002 SP3 using File/Get External Data/Import. (Am not choosing "Link Tables"). It gets imported as Type Table: Linked Paradox. When I then open the table for a datasheet view, the following happens: (1) datasheet window appears with field headings and normal-appearing data in all records and fields (2) error msg appears "Reserved error (-5016), there is no message for this error" (3) When I close the msg box, all field data gets replaced by #Name? I can open the table in design view, but no properties can be edited.
hi i have an application that has to import data from paradox tables and create reports based on those tables. I am using Access 2003 and the paradox database is 4.0 . I know how to import a batch of files from code but my problem is that the paradox database has some tables that are split in different folders according to the month they were recorded (it's an accounting program ) so a table exists with the same name in each month folder and the problem is that they have id's starting from 0 each month so I cannot append them easily I do not know how many tables that type I will need so I have to keep track of them through a different table so I cannot create individual queries for them.
I need to export a table from Access to a Paradox DB file for use with an ancient program that unfortunately we're still running. The problem I have is that the table must be created precisely as stated in the programs manual, which means the fields must not only be named exactly but also the type and size.
I've managed to do this...almost, the only problem I have at the moment is that I can't get Access to export date fields that Paradox will see as a date field, Paradox reads them as a timestamp field. I've tried setting them as a short date, integer or formatted text but Paradox simply won't accept them as a date type.
The whole purpose of this exercise is so Paradox won't even need to be opened if I can export this table correctly, but at the moment the only way to sort it is to open Paradox and change the field types manually.
Does anybody have any clue how I can successfully export a date field from Access that Paradox will see correctly? Ironically there isn't even any data being stored in these date fields, but the program won't run unless they exist and are of type D!
I have my database connected to a network of ten computers. I recently switched my linked tables from a Mapped Network Drive to using the actual UNC path \computerfolderdatabase.mdb
My users have started to notice it takes longer for the database to connect in order to log in. Once they have established the connection, the data transfer speed seems to be normal.
Is this to be expected? Any suggestions to speed things up for login? Or is this the downside to using UNC?
I have searched this site but could find no similar questions. SO..
I am converting an Access 97 database to Access 2003. I have compacted the 97 database before doing anything else.
The size of the 97 database is 91Mb
I have gone into Access 2003 and performed a database utilities>convert database>To Access 2002-2003 format and it has produced an 03 database with a size of 68Mb
I have also created a blank 03 database and imported all objects from the 97 database, changed all the text/memo fields to Unicode Compression = Yes and compacted the new 03 database and the size is 90Mb
What is the Auto conversion process doing that I aren't doing when importing objects that saves it an extra 22Mb? Plus is there anything I can do to free up that extra 22Mb again?
I'm having a number of tables in Access which I want to populate with data from excel/txt. In my import files I have some columns which contain alphanumeric data, like 0001 or XYZ0.
I've defined these columns as text in the definition of my table, however whenever I'm importing the text file, it converts those rows that can be read as a number to a number prior to storing it in my table. Hence values like 0001 becomes 1. Which is absolutely not what I need.
How I can prevent Access from doing this conversion? Why does it do the conversion anyway? I wouldn't expect any conversion since I defined the column as text...
When I import the same txt file into a new table (created during import, where I also define those columns as text) everything goes fine, 0001 stays 0001, but I don't want to remove my table and redefine it during the import everytime I need to import new data.
Am just trying to set the default value (on the form, not programmatically) of a text box to a date but with every attempt it either fails or sets the date to 1905-randmon month & random day.I've tried a few different methods from various online sources.
=Now() works fine.
Any attempt to set to an actual date returns 1905-Random Month-Random Day?I am trying to set it to the 1st day of the current month.Text Box is formatted as Short Date - Regional settings are set to the ISO standard numeric date format YYYY-MM-DD.
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
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.......
