Page setup for a report keeps changing

  • Thread starter Thread starter Rusty Shackelford
  • Start date Start date
R

Rusty Shackelford

I have a database that has multiple people using it. There is a report that
prints a envelope, but the page setup of the report keeps changing from
envelope. It happens randomly and is very annoying as everyone needs to get
out of it to change it and it doesn't stay anyway. Any solution out there?
 
You should be running a split database, and installing the "mde" part on
EACH pc.

If you don't do the above...you can have all kinds of problems.

As for the printer settings, you can turn off AutoCorrect.

However, even better is to turn off auto correct, AND install the office
sr-1a updates, as this update fixes all kinds of bugs, and will make your
application a LOT more stable,a and reduce support costs.


Check the follwing:

ACC2000: Lost Printer Settings When Name AutoCorrect Is Enabled
http://support.microsoft.com/default.aspx?scid=kb;en-us;240826
 
The page setup will reset to default if the printer is not there when
you try to use it, or if you are using an old unpatched version of
Office 2K.

Actually, Access talks to the 'printer driver', so the page setup will
reset to default if the 'printer driver' is not there when you try to
print.

That means you need to have exactly the same printer driver. That means,
among other things, that you need to all have the same version of Windows.
That means.... that you should each have your own copy of the database,
and you shared data only (linked tables).

You can also test in your application to see that no-one is using a faulty
copy of Office 2K. Testing is the only way to be sure:

----------------
This is a dll version checker for use inside an application.
Note that it does not include a path to the DLL. by default,
it finds the version of the DLL that has been loaded into
memory by the application. You can modify this code so that
it always displays the version number of the files it checks.

'David Graham. (david) Right to attribution retained.
'Watch for word wrap

Option Compare Database
Option Explicit
Const mcModuleName = "mdlRP_DLLCheck"
'2003/02/26 dlg
Private Declare Function GetFileVersionInfo& Lib "Version" Alias
"GetFileVersionInfoA" (ByVal FileName$, ByVal lptr&, ByVal lSize&, lpvData
As Any)

Public Sub gsbDLLCheck()
If ("4.0.7328.0" > gfn_GetVersion("msjet40.dll")) Then MsgBox "Warning:
MSJET40.dll is " & gfn_GetVersion("msjet40.dll") ' & ", not SP7"
If ("9.0.0.3822" > gfn_GetVersion("msaccess.exe")) Then MsgBox "Warning:
MSACCESS.EXE is " & gfn_GetVersion("msaccess.exe") ' & ", not SR1"

End Sub

Public Function gfn_GetVersion(FileName$)
'2003/02/26 dlg --minimalist version -- Right to attribution retained
Dim iBuf(0 To 99) As Integer
Call GetFileVersionInfo(FileName$, 0&, 200, iBuf(0))
gfn_GetVersion = iBuf(25) & "." & iBuf(24) & "." & iBuf(27) & "." &
iBuf(26) 'FILE VERSION

End Function
 
Office is all patched up and I don't think that is the problem. As far as
spliting the database, we have recently got SQL server and I am trying to do
the upszing wizzard but it fails and does not tell me why. So there is no
way to fix this other than dadicaly changing the current setup?
 
Office is all patched up and I don't think that is the problem. As far as
spliting the database, we have recently got SQL server
Click to expand...

When we speak of splitting the database, you don't need sql server, and sql
server has nothing to do with the splitting process.
So there is no
way to fix this other than dadicaly changing the current setup?
Click to expand...

It is VERY easy to run the wizard that splits your database. You don't need
any new software, and none of your application code will need to be changed.
Likely your problem is that one bad user is changing the printer, or perhaps
you have one bad miss behaving pc is re-setting the printer stuff. Of
course, if you had a split database, then that one bad pc would NOT bring
down the whole house like it is now.

Remember, you always installed word on EACH pc. You always installed Excel
on EACH pc. You might share some word, or Excel documents on your
server...but the word, and Excel software is RUN ON EACH PC!

Application gets installed on each pc

Data can be shared on the server

Now, you are using tools to create software! You now are writing software
just like the developers did to create word, or Excel. That software just
like Word, or Excel needs to be installed on EACH pc. If you don't, then one
bad pc can mess up the whole party for everyone. Can you imagine if one
person had a problem with word..and all users got the boot?

Basically, either you adopt the standard practice of installing the software
on each pc, or you kind have to give up on the software idea...(back to pen
and paper!).

So, I would try splitting your database. You don't need server to do this,
and it allows you are much better control over software updates. In fact,
you can develop on a new front ends at will, and are free to prepare the
next great version or update to your software. Your users in the meanwhile
can happily work on the known good production copy.

So, not only is a split database a good thing from reliability point of
view, but it makes the process of development a lot easer. And, it is zero
cost...as we are not talking about sql server here...

If you are new to splitting, try reading the following info, it will help
you understand what is meant here...

http://www.granite.ab.ca/access/splitapp.htm

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm


Also, if you patched office...then you still need to ensure that track name
auto-correct is turned off.

Further...each user should be getting a mde front end...
 
changing to a Front End / Back End linked table setup is easier than
changing to SQL Server. Use the database splitter wizard.

The failure of the SQL upsizing wizard is often due to faulty data
or in-appropriate table design. If you haven't done this before,
at least have a look at http://www.ssw.com.au/ssw/UpsizingPRO/
There is a downloadable demo version which may help you.

(david)
 
Thanks for all your input. I will look at splitting the database as a
temporary solution but in the long run I want to setup SQL for the learning
EXP and because opening an Access file over a WAN link is slow. Thanks So
Much
 
Back
Top