My company is about to join the 21st century and they are upgrading from MS Office 97 to XP and Office 2003.
We have lots of Access databases, many designed by me, so if they don't work next Monday people will start comming to me for answers. As I am only familiar with Access 97 (and I am by no means an expert, even though everyone thinks I am!) are there any problems I can expect when we upgrade to the latest version?
Any tips appreciated.
I have an old database that is in use based on this one I have created a new one next to it with test data in it. How can I place all data in the new data base there are in some tables new colums added?
View 1 Replies View RelatedI have an access db in a small lan (12 clients)
I want to make an upgrade and to go to an more powerfull tool than access
It is possible to do that easy with mysql sql server ........... or something else ?
Thank you
Please help?! We just upgraded from 97 to 2003 version. This is a scheduler routine which auto imports an excel spreadsheet into our main db. After I upgraded it stops on with "compile error variable not defined" Also after the conversion ...there was an error that said "May be due to old DAO syntax that is no longer supported" l am pasting the module code below but this line is where I get the error:
FileFormat:=xlexcel9795, Password:="", WriteResPassword:="", _
I don't have any idea of what to do and this has to run every night.
CODE:
Public Function importisfile(imptype As String)
Dim importpath As String 'path for work or home
Dim impfile As String 'filename of xl import
Dim tempfile As String 'temporary for rewrite
Dim tblimptemp As String 'tablename
Dim stdocname As String 'conversion string
Dim stdocname1 As String 'conversion string
Dim recsetname As String
Dim XL As Object
Dim db As Database 'used in traversal
Dim rec As Recordset 'used in traversal
Dim tbltempstr As String 'table to traverse
Dim x As Integer 'used to count traversal
'importpath = "V:AdministrationImports"
importpath = "V:AdministrationImports"
impfile = importpath + "TOX" + "kit.xls" 'eg. c:importTOXCANkit.xls
tempfile = importpath + "TOX" + "kit2.xls" 'eg. c:importTOXUSkit2.xls
stdocname = "qryappendimportTOX" 'date conversion in this query
stdocname1 = "qrydeleteimportTOX" 'date conversion in this query
tblimptemp = "tblimporttempTOX" + "Kit" 'eg. tblimporttempTOXCANKit
tbltempstr = "tblTOX" + "kit"
On Error GoTo Err_imp1
Set XL = CreateObject("Excel.Application")
With XL.Application
.Visible = True
.Workbooks.Open impfile
.ActiveWorkbook.SaveAs FileName:=tempfile, _
FileFormat:=xlexcel9795, Password:="", WriteResPassword:="", _
ReadOnlyRecommended:=False, CreateBackup:=False
.Quit
End With
Set XL = Nothing
Kill impfile
Name tempfile As impfile
'transfers the readable xls file into access database
DoCmd.TransferSpreadsheet (acImport), acSpreadsheetTypeExcel97, tblimptemp, impfile
Hi everyone,
I recently added a new page to an existing database in 97. All the previous pages run with a case number. I then upgraded to access 2003 and now the case numbers are out of snyc on the new page.
Can anyone help.
Hey,
I'm recently starting a new job and one of my tasks is to clean up their Access 2000 database. After looking through it and realizing how much crap there is in it, I was thinking about starting a new one for them from scratch. I was wondering if there are any pros/cons to redeveloping the database in 2003 verses 2000. Its a pretty small company with usually about 6 people concurrently working on it throughout the day.
Any thoughts would be appreciated!!
Good afternoon (well, it is here in the UK)
We have just changed from Access 97 to 2000 (only 6 years behind) and I use a database that has this piece of code running:
Private Sub DateOfAction_AfterUpdate()
DoCmd.Requery
Forms![CallLogMain]![CallLogDetails]![Child68].Requery
Forms![CallLogMain]![CallLogDetails]![Child71].Requery
Forms![CallLogMain]![CallLogDetails].SetFocus
Forms![CallLogMain]![CallLogDetails]![CallID].SetFocus
End Sub
After the record was input 2 subforms would refresh to recalculate a field storing the total time and then it would set focus to the main form to allow you move to the next record.
Now the database has changed to 2000, this no longer works which is a pain in the bum.
Any ideas why this has happened?
Regards.
I have recently upgraded from access 200 to access 2003 and I am having a problem using my reports. I can run the querys just fine but the reports wil not run at all. I can't open them in design view either. Ant thought how to fix this.
View 3 Replies View RelatedHi everyone,
I'm new here and I have a problem I cannot solve. I tried searching for ideas, but I could not find any help.
Here is my problem.
I have a database form used to scroll through records. I use the same form for searching. The user clicks a search button, I clear the form, they enter their search criteria (perhaps in multiple fields). Since upgrading to 2007, the clearing of the form takes many times longer than it did in 2003. I am using the following code to clear the form.
For Each Ctrl In form.Controls
If TypeOf Ctrl Is TextBox Then
Ctrl.SetFocus
Ctrl.ControlSource = ""
Ctrl.Value = ""
End If
Next
This code executes instantly in 2003 and takes almost 1 minute in 2007. Any thoughts as to why this is so different in 2007?
If there is a different way I should be clearing the form, please let me know.
Thanks for your help.
I've got Access 2000 and was wondering what I needed to upgrade to Access 2007. By this I mean, front page of manual, ID code, etc. And is it something I have to present at purchase or something that Microsoft validates online. Does anyone know?
View 9 Replies View RelatedI have upgraded from Access 2003 to to 2007 in Window XP. When trying to edit code I get the message Project Locked - "Project is unviewable".
Sandy
Hi,
In 2000 and xp i used this code to count the rows of a sub form : -
subform_controlname.form.recordset.recordcount
this no longer works in 2003 and i just get #Name? appearing instead???
Any idea's on why that is??
Thanks
Adam
We keep having our backend tables corrupt. We want to upgrade only the backend tables to SQL server. I don't even know where to start. What version of SQL server? I guess I find out if we have an existing licence in the company? Any help on this?
View 4 Replies View RelatedI'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?
We just upgraded to Office 2007 and are experiencing very slow access performance. This microsoft article addresses the problem:
http://support.microsoft.com/kb/275085
It won't let me change Subdatasheet Name property to [NONE].
Even if I am able to change it, will this affect my table links. I have a lot of them.
I am just the part-time Access "programmer" here and am somewhat lost trying to figure this out. Does anyone have a simple explanation and solution? I would appreciate any help so much!!
Hi
At work I was just updated to access 2003. I am trying to update a data base that I created in access 2000. Whenever I try to open a data access page I get the following error. "The installer encountered an internal string error. Installation failed." I've updated the Web components and that seems to have gone ok. My IT people are at a loss.
Any suggestions?
Thanks
John
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 date field on one of my forms that gets populated automatically when a new record is created. I also have a subform on the form that lists the tasks that still need to be accomplished this month.
Some problems have popped up as people got new computers with new versions of Access:
Access 2002(10.6501.6825) SP3 - No problems.
Access 2002(10.6771.6817) SP3 - The Date field isn't recognised on a new record (#Name?), but it's fine on the old records (displays date).
Access 2002(10.6771.6825) SP3 - The reminder subform is blank (white), as if it doesn't exist, but the date field works fine.
Any ideas why this might be/how to fix?
Thanks! This is really frustrating. If it didn't work for anyone, I would find a way to fix it, but because it works for some people, I don't know what to fix...
I am in the process of upgrading Access b/e to SQL b/e using .mdb and linked table as the front end ( as given as the best solution in many of the posts).
I remember reading in this forum ( Comment made by Pat Hartman) that forms should be based on queries rather than using a filter criteria.
I have a continuous form with project records. The user can double click one of the records to view further details of the project on a separate form. The code I have used to open the form is as follows:
strdocname = "frmProjDetails"
strParm = ""
strLinkCriteria = "[WProjNo]=" & "'" & Me![ProjNo] & "'"
DoCmd.OpenForm strdocname, , , , acFormEdit, , strParm
Would this be a reduction in performance? Should the record source of the details form be changed to a query that has a where clause pointing to the selected record?
Thanks...Priya
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
HI, Im new to this, so I need some help if you can on the subject of upgrading a database created using access 1.0 to the latset version of access, can this be done ? Many Thanks
View 3 Replies View Related