Actually, later versions of ACCESS can be used to change the DATA. Just don't try to change the structure of the database itself. Do NOT convert the database to the later version. Make a backup of the database just in case.
73, Jim N6VH Paul Cassel wrote: > Frustrating and I agree that Jack needs to rethink how he secures his > software. I hate to tell you that this major issue has been beaten to death > and do-date, no one has been able to overcome this short of using Search and > Replace or using ACCESS 97 (nothing newer) to modify > > Paul > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:dxbase- >> [EMAIL PROTECTED] On Behalf Of Mike Kasrich >> Sent: Sunday, November 11, 2007 9:42 AM >> To: [email protected] >> Subject: [Dxbase] operator change addition >> >> I know you can manually change the operator but since I usually make 2k+ >> QSOs in each wpx it is impractical to change the operator for 15k qsos >> over the last 4-5 years. >> >> ______________________________________________________________ From [EMAIL PROTECTED] Sun Nov 11 18:43:24 2007 From: [EMAIL PROTECTED] (Gary Senesac AL9A) Date: Sun Nov 11 18:52:22 2007 Subject: [Dxbase] Global operator change References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> It can be done, but depending on how many other operator calls ended up the DXBase data it may be a pain. Fist, be sure to back up your log! Then, click on the first operator call you wish to change in the log. Click on Edit/Replace. The call sign you clicked on will already be filled in for you in the 'Find what:' line. In the 'Replace with:' line, enter AJ9C. Then click on Replace All. All instances of the call in the Operator field will be replaced with yours. Multiple iterations will be needed to change all the calls. Just remember the replace feature works down in the database, so be sure you are at the first instance of the call you are replacing or you may miss some. A work around may also be to do multiple find/replace changes to enter the call(s) you intend to delete into the Note field, or the Special-1, Special-2 field before doing the find/replace procedure to change them to your call. Then create or modify an existing label template to include the field with the other ops callsign. If you want to print a qsl card or label for that operator, use a unique Group identifier in the Pending Labels data base and then use your new template to print them out. I agree, it's a pain and I too wish there were a simpler solution around the security problem. Gary AL9A ----- Original Message ----- From: "Mike Kasrich" <[EMAIL PROTECTED]> To: <[email protected]> Sent: November 11, 2007 5:39 AM Subject: [Dxbase] Global operator change > The requirement that only a registered operator be listed in the operator > column in dxbase 2006 is quite user unfriendly. I have operated as multi > single in contests and the import reflects who was operating at the time > since we keep track of different statistics that way. When I go to print > a qsl for those contacts the operator isnt me they are excluded from the > print. I think this is something that needs to changed. Back to the > subject line of this message is there a way to change every contact to > list my call as the operator so all the [EMAIL PROTECTED] QSLs will print? > > Mike/aj9c > > ______________________________________________________________ > Dxbase mailing list > Home: http://mailman.qth.net/mailman/listinfo/dxbase > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected]
