Public Sub Amend_My_Field()
Dim myDb As Database
Dim TableName As TableDef
Dim TargetDB as string
TargetDB = “C:\MyFolder\MyDatabase.mdb”
Set myDb = OpenDatabase(TargetDB)
Set TableName = myDb.TableDefs![Schedule]
With TableName
.Fields.Append .createField("Temp...
Using the openEvent of the subreport test for the parent name, e.g. pName = me.parent.name
If the the report is opened as a report, i.e. not subreport, you will get an error (2452) which you can trap with error handling.
Hope this helps.
You could try setting the forms Recordset Type to Dynaset(inconsistent updates).
If that doesn't work then use your approach of updating each record with a different tab, changing the recordsource on the tab change event to the appropriate table (query).
The beforeUpdate is the place to put your code. As your code itself creates an update you are creating a never ending loop, e.g. afterUpdate update, afterupdate update etc.
The beforeUpdate is the place to put your code. As your code itself creates an update you are creating a never ending loop, e.g. afterUpdate update, afterupdate update etc.
The common dialog control cmdlg32.ocx will give you exactly what you are looking for. I am not sure if this comes only with the developer's version or whether other MS products provide it. If you have the ocx file above, it should be in windows system folder, reference it within your db and...
I haven't considered the logic of your code but try changing the forms recordset type to'Dynaset(inconsistent updates)'. This will sometimes allow updates to more than one table.
I cannot be 100% sure but I seem to remember reading that synchronizing using Replication Manager doesn't work with passwords.
Can I be inquisitive and ask why you are using replication across a Lan rather than linking the tables.
I am not sure why you need a sub report to display a heading, assuming I understand your question correctly, why can you not have the heading incorporated into the report bearing in mind that you have report and page headers, plus group headers if you need them.
You could then control the header...
Look at the functions Left, Right, mid, instr, instrRev (access 2000). These will allow you to manipulate the data, e.g.
A = left(myText,5)
If A = "Phone" then .......
To tab out of a subform forward is ctrl+tab, backwards is ctrl+shift+tab. All very user friendly.
An alternative is to use the onExit event of the subforms last control to set the focus to another control. e.g.
me.parent![mycontrol].setfocus
or me.parent![my other subform].setfocus
Once you have committed the transaction you cannot roll it back.
What I am suggesting is the other side of the coin, instead of checking that the update succeeded check whether it failed. If it failed then rollback.
Whilst the beginTrans to commitTrans phase is running record locks have to be...
I am not sure that Access provdies 'confirm updates' as some others databases do.
Set a boolean true as the first instruction following beginTrans, e.g. transStarted = true. Write all your update code. Perform commitTrans and set transStarted = false (i.e. finished).
In your error handling...
One way that you may be able to achieve what I think you're wanting, is to use a Query as the recordsource and define a fourth field using IIF. You will also have to use the Format function to get the appropriate display, e.g.
Field1 is text
Field2 is date
Field3 is currency
in the query...